diff options
| author | eunhhu <[email protected]> | 2026-09-29 13:58:30 +0100 |
|---|---|---|
| committer | eunhhu <[email protected]> | 2026-09-29 13:58:44 +0100 |
| commit | 0bbc12658c63f5f5fce2683798d4ac08b1e26e08 (patch) | |
| tree | b589d0b4c2adac20ec2d5180b0cfe865995cf4a9 /link/link.h | |
| parent | 9791a1e70979ee4ba832851912f0de20301343a8 (diff) | |
| download | pure-0bbc12658c63f5f5fce2683798d4ac08b1e26e08.tar.gz pure-0bbc12658c63f5f5fce2683798d4ac08b1e26e08.zip | |
Say what epochs cost a link, and what the search for it found (099)
Forward secrecy, 098's first task left: keys that leak later open only
epoch 0. M2 after the epoch began and after a restart is as before it
(p50 0.4 ms, p99 0.8 ms, the same CPU, no X25519 on restart). It costs a
p50 of 0.7-1.0 ms more while ten thousand devices first meet and for
about 40 s of accepts after, and a receiver that lost its memo now
stalls 0.8 s and catches up in 7.7 s, not 0.2-0.7: it lost the epochs,
and each sender opens one again. The search also found a packet more a
device from each of M6's path probe and the security checks' challenge,
and a load generator whose own pass over its devices was the floor of
the latency it measured. 098's note that epochs narrow KCI to the first
epoch was wrong; corrected.
Diffstat (limited to 'link/link.h')
0 files changed, 0 insertions, 0 deletions
