chore(trust): refresh ssh-allowed-signers and checksums - #63
Merged
on-unknown-fish merged 1 commit intoAug 24, 2026
Merged
Conversation
Regenerated ssh-allowed-signers from the current GitHub-published SSH keys for the existing signer roster (brng1151, chiro-hiro, bao-ninh-orochi, chirojr) and refreshed checksum.sha256 via the single source of truth. Roster (the trust boundary) is unchanged; only key material rotated by the signers themselves. Ran: ./generate-ssh-allowed-signers.sh
chiro-hiro
marked this pull request as ready for review
August 24, 2026 08:28
chiro-hiro
force-pushed
the
chore/regen-ssh-allowed-signers
branch
from
August 24, 2026 08:35
e473d43 to
d8612c2
Compare
on-unknown-fish
approved these changes
Aug 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refreshes the SSH trusted-signer allowlist from the keys the existing signers currently publish on GitHub, and regenerates the checksum manifest to match.
What changed
./generate-ssh-allowed-signers.sh, which refetchedhttps://github.com/<user>.keysfor the existing roster and rewrotessh-allowed-signers, then delegated togenerate-checksums.shto refreshchecksum.sha256.chiro-hiro4 → 5 keys,bao-ninh-orochi1 → 2 keys (signers rotated/added their own keys);brng1151andchirojrunchanged.Trust boundary
The signer roster (
GITHUB_USERS) is unchanged — no principal was added or removed. Only key material published by the existing, already-trusted signers changed. This mirrors prior refresh chores.Verification
sha256sum -c --strict checksum.sha256→ all OKssh-allowed-signersandchecksum.sha256in the diffIndependent
Touches: ssh-allowed-signers, checksum.sha256