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.

How it works Built by Rytter

$ unlock
reading the key from the clipboard
✓ the right key · in memory, not on disk
$ sec ssh-ed25519 | ssh-add -
Identity added: (stdin)
$ GH_TOKEN="$(sec github-token)" gh auth status
✓ Logged in to github.com (GH_TOKEN)
$ ls ~/.config/*/secrets
No such file or directory

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 sec as 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. 1

    Encrypt

    Each credential is a line in a sops file in git, so every change is a commit you can read.

  2. 2

    Unlock

    The one key lives in a password manager, not on disk, and enters memory once per login.

  3. 3

    Hand out

    Programs ask with sec as 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.

rytter.it All the things