diff options
| author | tv <tv@krebsco.de> | 2026-11-16 04:15:47 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 04:15:47 +0000 |
| commit | 7c746cf2f453c55f36cf479c2f098987c1618e03 (patch) | |
| tree | a503c37b26c0832421275468901ebd330acf3d70 /docs/federation.md | |
| parent | e707d90513f0555d64109e3b0b7945d7d757ef94 (diff) | |
federation: a node takes no token another node issued
A node took tokens from the nodes its party lists, and without a user
registry every user it lets in may do everything. A party's list is
written by a key its version names, or set by a version: so two thirds
of the parties, or a thief of that key, could list a node of their own
as the party's, issue a token under any name there, and have the party's
own nodes take it, against "the design rules nothing about what happens
on a party's own nodes". A node takes only its own tokens; a party logs
in to each of its nodes.
Diffstat (limited to 'docs/federation.md')
| -rw-r--r-- | docs/federation.md | 45 |
1 files changed, 22 insertions, 23 deletions
diff --git a/docs/federation.md b/docs/federation.md index 6bdc4e4..97a2c5f 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -224,11 +224,12 @@ topology (`neighbours`, `relays`, `topology`, `dissemination`), and whatever a l continuum adds. The topology is continuum's own, as the genesis change writes none; each node picks its own relays, and some of its neighbours by party (Nodes). Nothing but the policy is read of the rest. A member's change carries its node's signature, as -signatures are required in a strict swarm. A party logs in to its own nodes as its -operator sets up, and a node takes tokens only from the nodes of its own party (Nodes). -Whoever a node lets in through its API may have it commit what the rules take: -envelopes, whoever signed them, and the node's own protocol data; `--protocol-writers` -names nobody in a federated swarm. +signatures are required in a strict swarm. A party logs in to each of its nodes as its +operator sets up, and a node takes no token another node issued: a list naming a node as +its party's, which a version or a key the version names writes, opens nothing on the +party's own nodes. Whoever a node lets in through its API may have it commit what the +rules take: envelopes, whoever signed them, and the node's own protocol data; +`--protocol-writers` names nobody in a federated swarm. ### Changing the policy @@ -383,14 +384,13 @@ A party lists the nodes that carry for it, by node ID, at names, or set by a version as a version sets keys (Keys). A node's party is its operator's, in its configuration, and its own member entry names it. A node is a member while that party lists it: it registers, commits changes and syncs, and nodes sync with -members only (Stages); it takes tokens only from the nodes that party lists. Another -party's list does nothing. A party's list counts until the party writes another or a -version sets one, whatever keys its version names since, so that no change of keys -leaves a swarm without members; a list a stolen key wrote stays until the party writes -one under the version that replaced that key, which it can at once, through any member. -A node commits whatever envelopes it is given, its party's and others' alike: what -counts is who signed a value, not which node committed it. So a party without nodes of -its own writes through any node that takes its envelopes. +members only (Stages). Another party's list does nothing. A party's list counts until +the party writes another or a version sets one, whatever keys its version names since, +so that no change of keys leaves a swarm without members; a list a stolen key wrote +stays until the party writes one under the version that replaced that key, which it can +at once, through any member. A node commits whatever envelopes it is given, its party's +and others' alike: what counts is who signed a value, not which node committed it. So a +party without nodes of its own writes through any node that takes its envelopes. A node keeps some of its neighbours among its own party's nodes and those of the parties its operator names, so that a party listing many nodes can't be every node's @@ -645,7 +645,7 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang | 41 | A party withholding its changes or votes | Not promised | — | | 42 | Flooding: namespace, proposals, history, writers | Slow, not wrong | bench | | 43 | A node taken off its list writes changes at a history where it was on | Taken where valid there; behind what is written under later versions | unit | -| 44 | A token from another party's node | Refused: a node's party is its configuration's | unit | +| 44 | A token from another node, even one its party lists | Refused: a node takes only its own | unit | | 45 | A party lists another party's nodes, or one its party dropped | Nothing changes: a node is its own party's | unit | | 46 | A party lists many nodes, to be every node's neighbours | Each node keeps some among its own party's and those its operator names | sim | | 47 | A party's node writing another node's member entry | Refused: an entry is its member's | unit | @@ -784,15 +784,14 @@ On a federated swarm: node takes and the current one, judging by it; votes and proposals by their version's keys; the protocol data as listed, all else closed; the `cv3.` envelope with the meta's version, and the order by it; node lists, a node's party in its configuration, - and tokens from one's own party's nodes only; what every reading of a strict policy - in continuum (`strict()`) makes of the federated one; screening's frontier moved by - every change touching what the federation reads (versions, proposals, votes, key - sets, node lists), as `access::screen` moves it today for what continuum's rules - read; the byte formats (a version's JCS bytes, hashes in paths and how two compare, - the envelopes a version sets, the meta's version), and the sizes a version, a set, a - list, a path and a value may have, each within what a sync message carries. A node - that doesn't know the policy stops taking changes. Until stage 4, a federated swarm - takes no remake. + and no token from another node; what every reading of a strict policy in continuum + (`strict()`) makes of the federated one; screening's frontier moved by every change + touching what the federation reads (versions, proposals, votes, key sets, node + lists), as `access::screen` moves it today for what continuum's rules read; the byte + formats (a version's JCS bytes, hashes in paths and how two compare, the envelopes a + version sets, the meta's version), and the sizes a version, a set, a list, a path and + a value may have, each within what a sync message carries. A node that doesn't know + the policy stops taking changes. Until stage 4, a federated swarm takes no remake. 2. **What counts**, read by the current version and the keys; shown in the API. Reports of a party that voted twice, and of versions a node refused. 3. **Nodes**: membership by the node lists and the party a node's own entry names, the |
