In use · a workstation and four servers
Every secret in one file. One key opens it.
No key files scattered across a home directory: one encrypted file in git, one key you keep, and programs that ask as they run.
- 1 key, kept by hand
- 5 encrypted files
- 0 secrets on disk in plaintext
- 1 commit to rotate a token
Features
Nothing to find, nothing to leak.
-
One file per trust group
Yours, and one per server. Whoever holds a file's key reads all of it.
-
Asked for, not stored
Programs get their value from
secas they start. Nothing is left behind. -
Servers keep their own
Each box decrypts its own file at boot. Your key never leaves you.
How it works
sops and age, wired into Nix.
-
1
Encrypt
Each credential is a line in a sops file in git, so every change is a commit you can read.
-
2
Unlock
The one key lives in a password manager, not on disk, and enters memory once per login.
-
3
Hand out
Programs ask with
secas they run, so a rotated value reaches them with no copy to update.
Who built it
Built by Rytter.
I'm Jakob Rytter. I build software and run it, from the server to the screen, and secretsthing runs the machines I work on.