Skip to content

security: support update-signing key rotation #86

Description

@nextestudios

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

  • Multiple public keys in UpdateTrust; documented rotation procedure.

Controller UX

N/A.

Technical Notes

ControlFS.Infrastructure.Updates.

Acceptance Criteria

  • A manifest signed by either trusted key is accepted; others are refused.

Testing

Unit tests for new branches and for every bug reproduced before a fix (no trivial variations, see AGENTS.md).

Dependencies

  • None

Priority: low · Milestone: 9 · 1.0 Readiness

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: releasePackaging, signing, CI and releasesmoscow: couldMoSCoW: nice to have; after the Must/Should itemstype: securitySecurity hardening

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions