Security and privacy
Signed files
Everything the launcher installs is signed: packages, update manifests, entitlements, the catalog snapshot and price documents. A missing signature or an empty checksum is an error, never skipped. Ed25519 is used in the packaging code with test keys only; no production key exists in the repository and the key ceremony is not done. A revocation list and a trusted key set exist as code.
Built in the repository (checked files or tested library code; not a product you can run yet)
What to plan for
- Key ceremony not done
- Key loss
- Revocation travels with launcher updates
What the catalog lists
Planned items that match this topic (keyword match; read each as a pointer):
- Offline license verification SEC-0030
- Signed updates SEC-0031
- Signed everything: builds, updates, entitlements, catalog and price documents SEC-0047
- Signature is mandatory, no skip path SEC-0048
- Break-in tests per profile SEC-0054
- Offline license key (signed) LIC-0001
- Entitlement manifest LIC-0005
- Update signature verification LIC-0012
- Co-op tier counter LIC-0016
- Referral code redemption (signed token) LIC-0022
- Every package is sellable with an entitlement per package LIC-0037
- Entitlement file per package, signed and verified locally LIC-0038
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.