Back to articles

Tag archive

#licensing

L
Nov 16, 2026

Licensing an MSIX-packaged Windows app

MSIX is how Windows desktop apps get installed now — through winget, through enterprise deployment, through the Store — and it quietly changes three things a licensing SDK depends on. Writes to %LocalAppData% are redirected into a per-package folder the app never sees in a path. Uninstalling the package deletes that folder, so the cached activation lease, the local trial clock and the clock-tamper state disappear while the seat on the licensing service stays bound. And the install directory is read-only, which is exactly where a bundled site license should sit. This post walks through what the Keyright SDK writes and where it lands under a packaged app, why the machine fingerprint survives when the cache does not, what an uninstall/reinstall cycle does to seat accounting (nothing, thanks to idempotent activation — unless the customer meant to move), how to detect package identity and give the SDK explicit paths, how to ship a license inside the package, when to disable write virtualization in the manifest, and the test loop that proves it.

Nov 16, 202615 min read0 reactions0 comments
L
Nov 16, 2026

Licensing a .NET app on Linux and macOS

Most licensing guidance is written for Windows, and the Keyright SDK quietly hides that: the same Validate() and ActivateAsync() calls work on Linux and macOS. But the three things a licensing SDK depends on — a per-user data folder, a stable machine identity, and an app that relaunches often enough to refresh its lease — all look different off Windows. The lease lands in ~/.local/share, which a sandboxed Mac app or a systemd service with ProtectHome= cannot write. The machine fingerprint anchors on /etc/machine-id or the IOPlatformUUID instead of a registry value, and a golden image that forgot to clear machine-id makes a whole fleet one machine. And a daemon that starts once a quarter never gets the startup refresh a desktop app relies on, so its 14-day lease expires with the process still running. This post walks through where the SDK writes on each platform, what the fingerprint is built from and the two machine-id traps, a systemd unit with StateDirectory= and LoadCredential= that gives the SDK a home, the lease-refresh loop a long-running service needs, the file mode the lease deserves on a multi-user host, and the verification loop that proves it.

Nov 16, 202619 min read0 reactions0 comments
L
Nov 16, 2026

License every version from one key pair

Rotating your signing keys for each major version is the trap: it breaks older builds, forces a mass migration, and gives you no per-customer control. The better model keeps one key pair for the life of the product and carries what a license may do — which versions it runs, which features it unlocks, how much it may use — in signed entitlements. This post shows the three patterns with real code, how the grants stay tamper-proof online and offline, and when to reach for full release coverage instead.

Nov 16, 20266 min read0 reactions0 comments
D
Nov 16, 2026

Delegation chains let resellers mint their own keys

You sign a distributor contract and the first integration question is "how do our resellers issue keys to end customers?" The two obvious answers are both wrong: hand each reseller your root signing key and one leaked laptop forges your entire catalogue, or route every reseller sale through a live call to your issuing service and your partners cannot sell when you are down. The design that holds is a delegation chain — give each reseller a signed certificate that carries their own public key and a scope they may never exceed, let them sign end-customer licenses with the private half, and have the client verify the whole chain offline against one pinned root key. This post builds that chain in Keyright: the delegate certificate and its scope, how a reseller issues within it, the SDK verification that walks license to delegate to root, the rule that scope can only ever narrow, and why revoking one certificate silently expires every key a compromised reseller ever issued.

Nov 16, 202610 min read0 reactions0 comments
S
Nov 15, 2026

Scoping a Keyright license to an environment

The same license file tends to flow from production into staging, onto a developer laptop, and through CI, until nobody can tell which environment a validation came from and a leaked staging key quietly unlocks production. This is a migration guide: compare the three ways teams separate environments — a product per environment, a bare file per environment, and one product with a signed env entitlement — then move to the last one on Keyright without a flag day. It covers where the app learns its own environment (IHostEnvironment and the DOTNET_ENVIRONMENT / ASPNETCORE_ENVIRONMENT fallback), a twenty-line gate that fails closed on an unknown environment, a backward-compatible rollout where an unscoped legacy key still runs anywhere, and the honest limit: the environment is self-reported by your own config, so this is hygiene and clean telemetry, not a wall against an operator who sets the variable.

Nov 15, 202611 min read0 reactions0 comments