diff options
| author | tv <tv@krebsco.de> | 2026-11-15 20:18:07 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-15 20:18:07 +0000 |
| commit | 9ebdd9011d086bc74351c527f6626fe403ef3348 (patch) | |
| tree | 00157c5de9b899f5b0f4ce4bcf130222a8cba9bb /src/clock.rs | |
| parent | cb3ccc5c6107cc4fd96c4d7b184cc9b811857db1 (diff) | |
rules: a strict swarm stays strict
A strict policy could be written over with one that isn't, or deleted,
by a user who may manage the policy. While the swarm was relaxed so,
nothing was asked of the time before it turned strict: a change written
beside that turn was taken, and once the swarm turned strict again,
built on, a node judging that change while strict from the first turn
(one back from away, a joiner) refused it, and every node it told
dropped it with the second turn and everything after.
Under a strict policy, the policy is now written again only as strict:
an envelope there whose value isn't a strict policy, a signed `null`
among them, is refused. So a strict swarm has one change that turned
it, and the time before it stays closed; to leave it, start a new swarm
from its content. A swarm that isn't strict writes its policy as it
did.
Diffstat (limited to 'src/clock.rs')
0 files changed, 0 insertions, 0 deletions
