Skip to content

chore: refresh ssh-allowed-signers and checksums#55

Merged
chiro-hiro merged 1 commit into
orochi-network:mainfrom
chiro-hiro:chore/refresh-trust-anchors
Jun 4, 2026
Merged

chore: refresh ssh-allowed-signers and checksums#55
chiro-hiro merged 1 commit into
orochi-network:mainfrom
chiro-hiro:chore/refresh-trust-anchors

Conversation

@chiro-hiro

Copy link
Copy Markdown
Contributor

What

Regenerated ssh-allowed-signers and checksum.sha256 by running the generator scripts against the current GitHub-published SSH keys:

./generate-ssh-allowed-signers.sh   # fetches *.keys for each GITHUB_USERS entry, then refreshes checksums
./generate-checksums.sh             # single source of truth for checksum.sha256

Security-relevant delta

These files are a trust boundary (every listed key becomes an authorized commit signer), so the changes are spelled out:

  • chiro-hiro: 4 → 2 keys — dropped the sk-ssh-ed25519 security key and two older ed25519 keys; two current ed25519 keys remain.
  • chirojr: single ed25519 key rotated (replaced).
  • checksum.sha256: updated to match the new ssh-allowed-signers digest.

The set reflects exactly what each account currently publishes at https://github.com/<user>.keys — the script's source of truth. No manual edits.

Notes

The trust-anchor drift check (GPG allowlist vs SSH signers) emits informational warnings only; SSH trust is intentionally not auto-expanded from the GPG list.

Regenerate ssh-allowed-signers from the current GitHub-published SSH keys
and refresh checksum.sha256 through the generator scripts.

This picks up rotated signing keys:
- chiro-hiro: 4 -> 2 keys (dropped the sk-ssh-ed25519 security key and two
  older ed25519 keys; two current ed25519 keys remain)
- chirojr: key rotated (single ed25519 key replaced)

Both files are produced by generate-ssh-allowed-signers.sh /
generate-checksums.sh and committed verbatim.
@chiro-hiro chiro-hiro merged commit 136c6de into orochi-network:main Jun 4, 2026
4 checks passed
@chiro-hiro chiro-hiro deleted the chore/refresh-trust-anchors branch June 4, 2026 10:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant