aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/keys.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-18 12:31:09 +0000
committertv <tv@krebsco.de>2026-11-18 13:34:43 +0100
commit13d96ce6ecd386ddd39b803ecb52a8557476f8fa (patch)
tree3b1b946457dbb6073119a7be1b35d7d57934c804 /docs/guides/federation/keys.md
parent114739426a34654f1d296ed38040e369737775b2 (diff)
continuum-party keys, nodes: shown given no change, --set, --force
`keys` and `nodes` alone (`--list`) show the party's key set or node list as it counts at the node, one a line, without a key. `--set` writes it whole, none twice, in place of the arguments that did; `--add` and `--remove` change it as it counts. A set or list left empty, whichever way (`--set` with none, `--remove` of the last), is written with `--force` only: none of the party's writes count without keys, nor its nodes as members without a list.
Diffstat (limited to 'docs/guides/federation/keys.md')
-rw-r--r--docs/guides/federation/keys.md17
1 files changed, 9 insertions, 8 deletions
diff --git a/docs/guides/federation/keys.md b/docs/guides/federation/keys.md
index 6f9fc10..7f5bd7a 100644
--- a/docs/guides/federation/keys.md
+++ b/docs/guides/federation/keys.md
@@ -18,16 +18,17 @@ So keep the keys a version names apart, offline, on one machine with the party's
```sh
ssh-keygen -t ed25519 -N '' -f laptop.key
continuum-party --node http://tv:secret@localhost:3000 --key tv.key --record tv.record \
- keys "$(cat laptop.key.pub)" "$(cat desk.key.pub)"
+ keys --set "$(cat laptop.key.pub)" "$(cat desk.key.pub)"
continuum-party --node http://tv:secret@localhost:3000 --key laptop.key \
--record tv.record write home/tv/motd '"from the laptop"'
```
-Each key goes as one argument, an `authorized_keys` line; its comment is left out. With
-`--add` and `--remove` instead, the client writes the set as it counts at the node with
-those keys added or taken off (`keys --add "$(cat phone.pub)"`). A set holds up to 16
-keys, signed with a key the current version names for the party, which the client checks
-first. A node voting by itself keeps a key its version names on that
+Each key goes as one argument, an `authorized_keys` line; its comment is left out.
+`--set` writes the set whole; `--add` and `--remove` write it as it counts at the node,
+with those keys added or taken off (`keys --add "$(cat phone.pub)"`); `keys` alone shows
+it. A set left empty, so that none of the party's writes count, is written with
+`--force` only. A set holds up to 16 keys, signed with a key the current version names
+for the party, which the client checks first. A node voting by itself keeps a key its version names on that
node (`--store-vote-key`), an Ed25519 key in a file: one stolen there votes for the
party.
@@ -69,7 +70,7 @@ A write counts only while the key that signed it is among the party's keys: what
signed counts no more once the party's set drops it, wherever in history it is. So
before dropping a key, sign again with a new one what should stay:
-1. Write a set with the new keys beside the old.
+1. Add the new keys to the set, beside the old (`keys --add`).
2. Write again, with a new key, every value the party wants kept, on heads that hold that
set (the client signs on the heads its node shows). For a namespace:
@@ -82,7 +83,7 @@ before dropping a key, sign again with a new one what should stay:
done
```
-3. Write a set without the old keys.
+3. Take the old keys off the set (`keys --remove`).
A key added back, from a backup say, brings back what it signed, where nothing the party
signed since replaced it and no checkpoint left it out.