Security and privacy
Secure updates
Updating without a mandatory internet connection, with rollback. In the launcher library: a signed manifest with expiry and a rollback-protection sequence, a mandatory checksum, a list of blocked versions, staged download then rename, successor files (the running program is never overwritten), real rollback to a previous generation and automatic rollback after a failed first start, and install from a signed file. Tested with a mock fetcher; the HTTP fetcher and screens are not built.
Built in the repository (checked files or tested library code; not a product you can run yet)
What to plan for
- Failed update
- Offline update media
- No HTTP fetcher yet
What the catalog lists
Planned items that match this topic (keyword match; read each as a pointer):
- Pre-update automatic backup DATA-0022
- No outbound network by default SEC-0028
- Signed updates SEC-0031
- Signed everything: builds, updates, entitlements, catalog and price documents SEC-0047
- Tentative flat shared fee above the profit threshold (D29) LIC-0003
- Update delivery by file/USB LIC-0010
- Update delivery by direct download (opt-in) LIC-0011
- Update signature verification LIC-0012
- Update rollback LIC-0013
- Staged update (canary on one device) LIC-0014
- Offline licence semantics: updates_until (reserved, enforcement open) LIC-0044
- Quarterly cost model as signed data LIC-0052
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.