-
Notifications
You must be signed in to change notification settings - Fork 0
security: support update-signing key rotation #86
Copy link
Copy link
Open
Labels
area: releasePackaging, signing, CI and releasesPackaging, signing, CI and releasesmoscow: couldMoSCoW: nice to have; after the Must/Should itemsMoSCoW: nice to have; after the Must/Should itemstype: securitySecurity hardeningSecurity hardening
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
area: releasePackaging, signing, CI and releasesPackaging, signing, CI and releasesmoscow: couldMoSCoW: nice to have; after the Must/Should itemsMoSCoW: nice to have; after the Must/Should itemstype: securitySecurity hardeningSecurity hardening
Summary
Accept a set of trusted update keys so the signing key can be rotated without breaking automatic updates.
Motivation
The private key exists only in a GitHub secret; losing or leaking it would otherwise require manual reinstalls.
Requirements
UpdateTrust; documented rotation procedure.Controller UX
N/A.
Technical Notes
ControlFS.Infrastructure.Updates.Acceptance Criteria
Testing
Unit tests for new branches and for every bug reproduced before a fix (no trivial variations, see AGENTS.md).
Dependencies
Priority: low · Milestone: 9 · 1.0 Readiness