From d2f72861bacf22542ceb29297ccd97dc440a608e Mon Sep 17 00:00:00 2001 From: tv Date: Sun, 15 Nov 2026 21:38:04 +0000 Subject: config: a strict swarm starts empty `--genesis --remake` writes the content as a change of its own before the one recording the first users and `--bootstrap-policy`. With a strict policy, that content change was a time before the policy, on which any member could build a change judged by none. A strict `--bootstrap-policy` with `--remake` is now refused: a swarm strict from its start starts empty, and one started from content turns strict through a strict remake, which keeps only what an operator looked over. A policy that isn't strict starts from content as before. --- docs/access.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/access.md b/docs/access.md index 75f8db2..29b4cb6 100644 --- a/docs/access.md +++ b/docs/access.md @@ -54,9 +54,10 @@ may do nothing until added (the genesis node warns of those of its `--htpasswd`) log in by key and sign values from the start, and with `--bootstrap-policy '{"version": 1, "values": "signed"}'` the policy (Values signed by their users, below) in the same change: the swarm is strict from its start, and no -change of it is from before the policy. Started from content (`--genesis --remake`), -the content is a change of its own just before that one; a change built on it beside -that one is refused as from the time before a strict policy (below). +change of it is from before the policy. So it starts empty: content (`--genesis +--remake`) would be a change of its own before that one, and is refused with a strict +policy; a swarm started from content turns strict through a strict remake (Turning a +swarm strict, below). 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