diff options
| author | tv <tv@krebsco.de> | 2026-11-16 11:09:24 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 11:09:24 +0000 |
| commit | 2e0b0071e68d03942d1a4a7258d67a9d2fd30dd0 (patch) | |
| tree | 34479f75e0bbf332f81edc25f1c24b0cb97c97e1 /src/access/bans.rs | |
| parent | ff2da13601f8055d037758fd8c1056db6185f106 (diff) | |
federation: what an end-to-end read found at odds
Read whole after the last series of changes, the design said a few things
that no longer fit what it says elsewhere:
* the example's version 7 named lass's keys anew at 4 but gave lass no
node list, where a party new in a version has its list named anew;
* a remake reaches no node that can't build it, nor one that isn't to
follow it (not a member at the base, its coordinator unlisted);
* the clause on whose word follows a decision sat after a colon meant for
the abort;
* what a node taken off its list could commit before a base ends with the
remake only where the base holds that list;
* a remake racing a listing leaves behind the nodes listed since the base,
not "the nodes that took it";
* "Why it holds" now names the coordinator's listing;
* attack 29: a node that lacks the base syncs it where a peer keeps it;
* forks come at stage 4, so before it no swarm starts afresh by one;
* a party drops a stolen key of its set itself; only one its version
names takes a version.
Diffstat (limited to 'src/access/bans.rs')
0 files changed, 0 insertions, 0 deletions
