dpi-detector/scripts
Kirill Minovsky ff90794a57 stand: the QUIC gate, its three ladders and the browser deadline
What the day's captures settled, written where the next pass can find it. The
unopenable first reply is the local desync's fake, not an endpoint behaviour; the
fake leaves with the flow's own 5-tuple and one DCID, so the edge holds a single
half-open connection and its timeout is the gate. The gate is 2.5–3.5 s, not the
4.7 s the probe's ladder lands on: the probe's fourth send is the first after it,
curl's third (3.5 s), and Chrome closes itself at 4.004 s of silence, half a
second before its own next retransmit — so a browser cannot show the gate, only
fail on it (`ERR_QUIC_PROTOCOL_ERROR`, the netlog is quoted in the section).

The levers that would remove the gate are written down with what is measured and
what is not (badsum, a TTL, a host list built by measurement, an unpadded fake),
and the tester section points at the list the detector now ships. `replay.py`
stops crashing on the long headers that are not Initials.
2026-10-02 04:16:12 +03:00
..
quic stand: the QUIC gate, its three ladders and the browser deadline 2026-10-02 04:16:12 +03:00
bench-strategies.sh feat(bench): let a run set the detector's check timeout 2026-09-17 09:37:52 +03:00
vendor-advisories.sh crypto: the provider is ring, and the pure-Rust rule goes with it 2026-10-01 16:48:03 +03:00