1.8 KiB
Signed updates and rollback
The control plane returns a platform artifact URL, SHA-256, channel, protocol version, rollout percentage, pause flag, and Ed25519 signature. The updater must verify, in order:
- Ed25519 signature over the canonical manifest with an embedded/pinned public key.
- Downloaded artifact SHA-256.
- Native OS signature: Authenticode, Apple Developer ID plus notarization, or Linux package signature.
- Platform/architecture and protocol compatibility.
Do not replace binaries while an upload or commit is active. Keep the previous verified package for rollback. An administrator may pause rollout or pin a device group.
Default progression:
| Stage | Population | Observation |
|---|---|---|
| Canary | 5% | 24 hours |
| Pilot | 20% | 24 hours |
| Stable | 100% | continuous |
The management API makes release payload fields immutable after registration. Administrators may only switch the channel/fixed percentage (canary=5, pilot=20, stable=100) or pause/resume that signed record; the Web console exposes those guarded actions. Promotion is rejected until the current active stage has been observed for 24 hours. Paused time does not count: resuming restarts the observation clock. Rollback to an earlier stage remains immediate. Stage promotion is deliberately operator-confirmed because v1 has no trustworthy client crash telemetry feed.
Advance only if crash-free daemon rate, upload/commit error rate, audit continuity, and conflict rate remain within the release threshold. Rollback disables the new artifact and reinstalls the previous natively signed package; it never reverts data objects.
The schema is update-manifest.schema.json. CI signing keys and notarization credentials must be injected from the CI key vault.