From 1cbb52add18de6f078f941fd2dce2f3ce6b5c6e2 Mon Sep 17 00:00:00 2001 From: Ryan Yin Date: Mon, 21 Sep 2026 20:51:13 +0800 Subject: [PATCH] docs(secrets): desktops and recovery_key have identical access recovery_key is a member of desktop_keys, so every group written as desktop_keys ++ ... covers both. --- secrets/README.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/secrets/README.md b/secrets/README.md index b8a64e33..6a1a5abe 100644 --- a/secrets/README.md +++ b/secrets/README.md @@ -22,12 +22,14 @@ decrypt all my secrets via `agenix`. Then, I can use them in this flake. ## Which Keys Go on a Secret -**Every secret must be decryptable by the desktops.** The desktops hold the trusted admin keys, and -they are where secrets are added, edited and rekeyed — including `agenix -r`, which has to decrypt -every secret in this repository first. Narrowing a secret to the servers alone breaks that. +**Every secret is decryptable by the desktops and by the offline `recovery_key`, and those two have +identical access.** The desktops hold the trusted admin keys and are where secrets are added, edited +and rekeyed — including `agenix -r`, which has to decrypt every secret in this repository first. +`recovery_key` is a member of `desktop_keys`, so one rule covers both: every recipient set is +`desktop_keys ++ `. -So every recipient set is `desktop_keys ++ `, and `desktop_keys` carries the -offline `recovery_key`; a lost host therefore never makes a secret unrecoverable. +That also means a lost host never makes a secret unrecoverable, and that narrowing a set to the +servers alone breaks the desktops and the recovery key together. The one exception is the desktop's own restic repository password (`restic-password-desktop.age`): `desktop_keys` alone, because the backup servers must not be able to read desktop data.