From af120b87c42ca56f69bbe6f8d27c023919742430 Mon Sep 17 00:00:00 2001 From: tv Date: Sun, 15 Nov 2026 16:43:53 +0000 Subject: swarm: a new swarm's policy recorded in its genesis change A swarm strict from its start had its policy written by its first user in a later change. A change is judged by the policy at its history, so any member could always add a change whose history is from before the policy: judged by none, needing no signature, taken whenever it comes. Since signed values are read by `seq`, an envelope planted there with the highest `seq` there is can never be followed: a ban, a user, a declaration, for good. `--bootstrap-policy JSON`, with `--genesis`, records the policy in the genesis change, with the first users: then no change of the swarm is from before it. It must be a policy this node knows, and a strict one needs `--bootstrap-keys`, or nobody could sign what decides who may do what. --- docs/access.md | 8 +++++--- docs/example.toml | 6 ++++++ 2 files changed, 11 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/access.md b/docs/access.md index 2f7fa5a..89e74d7 100644 --- a/docs/access.md +++ b/docs/access.md @@ -51,8 +51,10 @@ A swarm gets a registry from its start if its genesis node is given its first us 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`). 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. +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. 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 @@ -465,7 +467,7 @@ replaced: a registry whose entries hold the users' keys turns strict as it is. A means trusted as it is: whatever entries, policy and bans it holds then count, plain values and envelopes alike, checked or not, whoever wrote them before (under a policy that isn't strict, a member may write as any user). So a swarm is best strict from its -start (`--bootstrap-keys`, A new swarm, above); one already running turns strict +start (`--bootstrap-policy`, A new swarm, above); one already running turns strict through a remake (Turning a swarm strict, below), which keeps only what an operator looked over. Writing the strict policy into it directly trusts it as it is: look it over first (`continuum-signed verify` on each entry). A value there that isn't an envelope diff --git a/docs/example.toml b/docs/example.toml index 77b9c09..3e189fe 100644 --- a/docs/example.toml +++ b/docs/example.toml @@ -150,6 +150,12 @@ htpasswd = "/etc/continuum/htpasswd" # values (docs/access.md), so a swarm can be strict from its start. # bootstrap-keys = ["alice=ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAA… laptop"] +# With genesis: the swarm's write protection policy (docs/access.md), recorded in its +# first change with its first users, so that no change of the swarm is from before it: +# {"version": 1, "values": "signed"} makes it strict from its start, and needs +# bootstrap-keys. +# bootstrap-policy = '{"version": 1, "values": "signed"}' + # How log lines look: text (timestamped), journal (for systemd's journal: no timestamp or # colours, the level as each line's priority, for journalctl -p), or auto: journal when # stdout goes to the journal, else text. -- cgit v1.3.1