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/example.toml | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs/example.toml') 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