Repository navigation
feat(secrets): trinity's age key and the sensitive tier's secrets (#404) - #688
Merged
Merged
Conversation
`make secrets-init STACK=sensitive`, run on trinity on 2026-09-28, filled the sensitive rule's placeholder with trinity's public key and created secrets/sensitive.sops.yaml. Its seven values were set by hand on trinity. What was checked there before the copy, without printing a value: the file decrypts with trinity's key, it is encrypted to that one recipient only, and none of the seven keys is empty or still a change-me placeholder. VAULTWARDEN_ADMIN_TOKEN is an argon2id PHC string and ADGUARD_ADMIN_PASSWORD_HASH is a bcrypt hash. check_sops_rules.py maps the file to the sensitive rule, not the catch-all. The two files carry a public key and ciphertext, nothing else. The technical second's recipient joins this rule before the tier holds real data (ADR-0024), as #404 step 10 says. Refs #404 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Refs #404. Runbook §6 (
build-the-sensitive-tier-host.md).Changes
.sops.yaml: thesensitiverule'sREPLACE_WITH_SENSITIVE_AGE_PUBLIC_KEYplaceholder becomes trinity's public key,age1cpdxl6p4…tjtsw.make secrets-init STACK=sensitivewrote it on trinity. No other line changes.secrets/sensitive.sops.yaml: new. It holds the tier's seven values, encrypted to that one key.Checks run
On trinity, before copying, and without printing any value:
change-meplaceholder.VAULTWARDEN_ADMIN_TOKENis an argon2id PHC string, andADGUARD_ADMIN_PASSWORD_HASHis a bcrypt hash.check_sops_rules.pymaps the file to thesensitiverule, not the catch-all. That rule is the reason the placeholder existed: the catch-all would have encrypted the tier's secrets to the estate's key.On prometheus, after the copy:
check_sops_rules.pyandcheck_docs.pypass.Still owed
The technical second's recipient must join this rule before the tier holds real data (ADR-0024, #404 step 10).
🤖 Generated with Claude Code