scripts: sealing and opening in the reference client

continuum-signed seal and open, with age, for the readers declared or
CONTINUUM_READERS.

Auth plan M8.

1 files changed, 4 insertions, 0 deletions

diff --git a/docs/access.md b/docs/access.md
index 6f89b49..4a0fd0e 100644
--- a/docs/access.md
+++ b/docs/access.md
@@ -323,6 +323,10 @@ value signed by its user (Values signed by their users) holds the sealed value;
 signature is over the ciphertext, so every node checks who wrote it without reading
 it.
 
+`scripts/continuum-signed` seals and opens them too, with age: `seal secrets/db
+'{"password": "…"}'` seals for the readers declared there (or `CONTINUUM_READERS`),
+signed, and `open secrets/db` opens it with the user's key.
+
 It guards against mistakes, not against a writer: one who means to leak a value has
 it. A reader removed keeps what it read: values stay sealed for the readers they were
 written for until written again, sealed for those declared then. Which values there