From b6f815882a6d4a32c1198bd3666edaeaf1f7bca3 Mon Sep 17 00:00:00 2001 From: tv Date: Sat, 7 Nov 2026 22:35:21 +0100 Subject: access: --bootstrap-keys The first users' SSH keys, recorded at genesis with their entries, so a swarm can be strict from its start. Auth plan M7. --- docs/access.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'docs/access.md') diff --git a/docs/access.md b/docs/access.md index a182266..d81f115 100644 --- a/docs/access.md +++ b/docs/access.md @@ -38,7 +38,10 @@ password hashes: every member reads the document). A swarm gets a registry from its start if its genesis node is given its first users, `--bootstrap-users`: it records them, with the swarm ID, in its first change, each with everything (`[]` and `["_continuum"]`). Other users, of its `--htpasswd` or any node's, -may do nothing until added (the genesis node warns of those of its `--htpasswd`). +may do nothing until added (the genesis node warns of those of its `--htpasswd`). With +`--bootstrap-keys alice=ssh-ed25519\ AAAA…\ laptop` it records their keys too, so they +log in by key and sign values from the start: a swarm whose first user then writes the +policy (Values signed by their users, below) is strict from its start. Without it, the swarm has no registry: its users are all alike (A swarm without a registry, below), until someone gives it one. `--protocol-writers` counts in both: without a registry, as who may write protocol data; with one, to set it right -- cgit v1.3.1