aboutsummaryrefslogtreecommitdiffstats
path: root/docs/access.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 02:15:50 +0000
committertv <tv@krebsco.de>2026-11-16 02:15:50 +0000
commit417e6ce3efbb1e32ee5443d1d77ec3f0d4874dc2 (patch)
tree89830f283aa4e5fb1a80acbc949fc5fd813c54a4 /docs/access.md
parentf37d2941415e12bc435265862e3fbdeec3206bd7 (diff)
docs/access: a strict policy given at genesis in the example
The example of a strict policy wrote it through the API, which every node refuses where the policy isn't strict: a swarm turns strict only at its start or through a strict remake. It shows the genesis node given the policy, with its first user and their key.
Diffstat (limited to 'docs/access.md')
-rw-r--r--docs/access.md8
1 files changed, 5 insertions, 3 deletions
diff --git a/docs/access.md b/docs/access.md
index dcd67f8..26026e9 100644
--- a/docs/access.md
+++ b/docs/access.md
@@ -420,11 +420,13 @@ curl -X PUT localhost:3000/store/_continuum/banned/<node ID> \
A member's node signs its changes, but the user a change names is its node's word: a
member could write as any user. A swarm can have its users sign the values that
matter themselves, with their SSH keys, so no member can write them but as a user
-signed them: the policy's `"values": "signed"` (strict; it requires signatures too).
+signed them: the policy's `"values": "signed"` (strict; it requires signatures too),
+given to its genesis node (A new swarm, above):
```sh
-curl -X PUT localhost:3000/store/_continuum/access/policy \
- -H 'Content-Type: application/json' -d '{"version": 1, "values": "signed"}'
+continuum --genesis --bootstrap-users alice \
+ --bootstrap-keys 'alice=ssh-ed25519 AAAA… laptop' \
+ --bootstrap-policy '{"version": 1, "values": "signed"}' …
```
Signed then are what decides who may do what (every user's entry, every entry of