From 4c823be0a7db145c43a8c67accfb6907b5d95361 Mon Sep 17 00:00:00 2001 From: tv Date: Wed, 18 Nov 2026 11:52:46 +0000 Subject: continuum-party keys, nodes: --add and --remove, and the key they need `keys` and `nodes` write the party's key set or node list whole, or, with `--add` and `--remove`, the set or list as it counts at the node with those added or taken off, each of which must change it; the client says what it writes. Node IDs are checked as the federation spells them. A set or list is signed with a key the current version names for the party: the client checks that first, and where it isn't one, or the party is none of the version, says that only a version naming the party's keys or list anew changes them, which a party proposes and the parties pass. --- docs/guides/federation/common-changes.md | 14 ++++++++++---- docs/guides/federation/keys.md | 7 +++++-- 2 files changed, 15 insertions(+), 6 deletions(-) (limited to 'docs/guides/federation') diff --git a/docs/guides/federation/common-changes.md b/docs/guides/federation/common-changes.md index acbd98a..1f7f331 100644 --- a/docs/guides/federation/common-changes.md +++ b/docs/guides/federation/common-changes.md @@ -86,15 +86,21 @@ jq --arg key "$(cut -d' ' -f1,2 tv-new.key.pub)" ' ## What a party does by itself -* **Its node list**, signed with a key its version names, no vote: +* **Its node list**, signed with a key its version names, no vote: the list whole, or the + list as it counts at the node with nodes added (`--add`) or taken off (`--remove`): ```sh continuum-party --node http://tv:secret@localhost:3000 --key tv.key \ - --record tv.record nodes continuum:5be1… continuum:77d0… + --record tv.record nodes --add continuum:77d0… + # tv's node list: continuum:5be1… continuum:77d0… + # 9b2c… taken ``` - A version names a party's list anew only where it must: when the party is let in, or - when it can't write its own. + The client checks first that the current version names the key it signs with for the + party, and says otherwise: then only a version naming the party's keys or its list + anew changes it, which a party proposes and the parties pass. A version names a + party's list anew only where it must: when the party is let in, or when it can't write + its own. * **Its key set**, likewise ([`keys.md`](keys.md)). * **Its writes**, wherever the rules give it places ([`writing-and-reading.md`](writing-and-reading.md)). diff --git a/docs/guides/federation/keys.md b/docs/guides/federation/keys.md index 3dd2834..6f9fc10 100644 --- a/docs/guides/federation/keys.md +++ b/docs/guides/federation/keys.md @@ -23,8 +23,11 @@ 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. A -set holds up to 16 keys. 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. 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 node (`--store-vote-key`), an Ed25519 key in a file: one stolen there votes for the party. -- cgit v1.3.1