diff options
| author | tv <tv@krebsco.de> | 2026-11-19 01:48:57 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 03:18:34 +0100 |
| commit | f24063e90d02ef76d87401d6e74cf8c9f489ff7d (patch) | |
| tree | 313fa30d2610a248f5132dfe1c2d3a37ce73f624 /src/api/stats.rs | |
| parent | c0bb757df50fe4aa025ba2e6ac021e179291c78b (diff) | |
fold: of a party's lists, those written under the latest version first
A key a version names, stolen, could write its party's node list at a history from
before the version that named the party's keys anew: written under the version before,
it counted, as naming keys anew leaves a list's `since` alone, and beside the list the
party wrote under the new version the lower ID won. The thief signed a few, kept the
lowest, and did so again after every list the party wrote.
Of a party's key sets, and of its node lists, those written under the latest version now
come first, then what no other has in its history, then the lowest ID; the model alike.
A list the party writes under the version that replaced the key stays, as `federation.md`
says. Key sets were safe already, by their `since`; one rule serves both.
This changes what counts where two of a party's lists, written under different
versions, are beside each other: nodes read them alike only once all run it.
Row 69 is tested (`federation_attack_69`).
Diffstat (limited to 'src/api/stats.rs')
0 files changed, 0 insertions, 0 deletions
