Fimeg/RedFlag
Watch
1
0
Fork
You've already forked RedFlag
 0
Code Releases Activity

ci: give release tags a key of their own

Browse source 
The old signer was minted for a forge this pipeline stopped publishing to, and a key that opens a host has no business vouching for a release.

The new one signs tags and opens nothing.
This commit is contained in:
Fimeg 2026-09-03 20:42:02 -04:00
commit 37a603ae14
1 changed files with 13 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

14
.gitea/allowed_signers
View file

@ -1 +1,13 @@
casey.tunturi@gmail.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJb7XowYoupqZoRTf0U4RKJcBH6DR+nKOocmoPRFaWf6
# Keys authorised to sign RedFlag release tags. The version gate in
# .gitea/workflows/release.yml verifies the tag against this file and nothing
# else, so this list is the whole of the release-signing authority.
#
# This key signs tags and does nothing else: it is absent from ~/.ssh/config,
# from every authorized_keys, and from any transport path. A key that opens a
# host should never also vouch for a release.
#
# Rotation: add the incoming key on its own line, cut one release that both
# keys can verify, then delete the outgoing line. ssh(1) allowed_signers also
# accepts valid-after= and valid-before= options when a key should lapse on a
# date rather than on a release.
casey.tunturi@gmail.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMLaHSap8O8lqv1ipvXC8F0QFBqAZF66Ombe/Ep8kX8M RedFlag release signing