Skip to content

Document repository privacy and secret rotation after a key leak - #42

Open
byjpr wants to merge 1 commit into
claude/admiring-planck-25cvzffrom
claude/fix-18-repo-privacy
Open

byjpr wants to merge 1 commit into
claude/admiring-planck-25cvzffrom
claude/fix-18-repo-privacy

Conversation

@byjpr

@byjpr byjpr commented Oct 9, 2026

Copy link
Copy Markdown
Owner

Closes #18

Changes

  • docs/security.md, section "Keep the repository private": settings.nix is a complete target list, and encrypted secrets are only as strong as the age keys forever, because every old ciphertext stays in git history.
  • docs/security.md, section "After a key leak, rotate the secrets, not just the keys": sops updatekeys only protects future commits. Step by step: replace the key (for the server key, also the host key files, then reinstall), updatekeys, then rotate every secret:
    • mailbox passwords;
    • DKIM keys via a new selector;
    • relay and backup credentials;
    • the Terraform state passphrase;
    • provider tokens.
  • just init ends with a reminder to keep the repository private.

Testing

All 5 provider example systems build. nixfmt, shellcheck and tofu validate pass.

🤖 Generated with Claude Code

https://claude.ai/code/session_01G22o7QQ17GRtkCqpJNFr9B


Generated by Claude Code

docs/security.md now explains why the repository must be private (the
mailbox list; ciphertexts living in git history forever) and that after a
key leak the secrets themselves must be rotated, with the steps. just init
reminds to keep the repository private.

Closes #18

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01G22o7QQ17GRtkCqpJNFr9B
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.

[Low] Repository contents: mailbox list exposure and git-history ciphertexts

2 participants