From 24527adf52ca2d8d3b927feb1b811e10fc55fc5c Mon Sep 17 00:00:00 2001 From: tv Date: Sun, 8 Nov 2026 22:43:19 +0000 Subject: signatures: sign what is sent A node signed its changes no rule signs a while after them (--sign-every 1s): the change left at once, unsigned, and its signature followed on its own a second later, to every neighbour, over every link. A few writes made a cascade of SIGNATURES. Under a policy requiring signatures it signed every change as it was made instead. A node now signs its latest change, if no signature vouches for it, as a sync message takes it (--sign-every sent, the default): the signature leaves in the same message, and goes where the change goes. One signature per message, however many changes it carries, each vouching for those before it: a slow writer's every change is signed, a fast writer's batches are, at no threshold to pick. A policy requiring signatures signs what is sent too, even with `none`. `all` still signs every change as it is made; changes to protocol data, listed paths and ?signed=true writes are signed as they are made, as before. The interval, and the task signing on it, go. --- src/node.rs | 3 --- 1 file changed, 3 deletions(-) (limited to 'src/node.rs') diff --git a/src/node.rs b/src/node.rs index 314433c..742da09 100644 --- a/src/node.rs +++ b/src/node.rs @@ -275,9 +275,6 @@ impl Node { tokio::spawn(remake::run_worker(state.clone())); tokio::spawn(crate::swarm::signatures::run(state.clone())); - if let crate::document::signatures::SignEvery::Interval(every) = state.sign_every { - tokio::spawn(state.clone().sign_latest_every(every)); - } trace!("Remake worker task spawned"); tokio::spawn(swarm::topology::run_worker(state.clone())); -- cgit v1.3.1