Skip to content

Security: systemlocker/System-Locker-Nightflyer-.NET

Security

SECURITY.md

Security policy

Report vulnerabilities privately through System Locker support. Do not include license credentials, installation private keys, leases, or customer data in a public issue.

Trust boundary

The application developer must embed an initial Nightflyer Ed25519 public-key ring through a trusted release channel. This SDK accepts a replacement key only through a signed, linear key-transition token whose old key is already trusted. It never discovers trust roots from an unsigned HTTP response.

Nightflyer verifies the signature and fixed token type before consuming lease or status claims. A valid offline lease remains valid until its signed expiry; an offline device cannot observe server-side revocation until it reconnects.

Accepted limitations

EcdsaInstallationKey is intentionally memory-only. Applications choosing persistent leases must store an imported/exported installation key in an OS-protected key store, bind their own persistence to the current OS user, and protect lease/state updates against rollback.

There aren't any published security advisories