2026-chen-closing-loop-bidirectional
Closing the Loop: Bidirectional Fully Encrypted Protocols
canonical link → · arxiv: 2609.17397
2026-chen-closing-loop-bidirectional
canonical link → · arxiv: 2609.17397
findings extracted from this paper
The Rust BiFEP reference implementation (≈20.4k lines: 2,195 datastream, 989 datagram, 813 shared, 16,375 harness) achieves 28.2 MiB/s goodput at 37.0 µs per epoch operation for datastreams, and 420 MiB/s at 1.36 µs per atomic send/receive for datagrams; all 62,119 conformance assertions passed across 491 trials and 5,321 logical epochs, with 0 forged semantics across 360 datastream and 120 datagram active-integrity trials.
The BiFEP datastream construction uses a 'wrapper' layer with authenticated DATA, DUMMY, and FIN frames over an independently keyed inner FEP per direction, revealing only a public sending schedule ΓX(t) and quantized closing epoch from the set Ecl — the exact private half-close time is hidden behind continued cover traffic. Empirical passive diagnostics on the Rust implementation show byte entropy of 7.999279–7.999749 bits/byte, maximum absolute byte correlation of 0.004668, and a random-forest ROC-AUC of 0.485 (95% CI [0.428, 0.542]) distinguishing DATA from ChaCha20 — not significantly better than chance.
For datagram-mode BiFEP (UDP), a configurable linger depth L prevents permanent one-sided close: without linger (L=0), one-sided ACK loss causes the peer that closed first to go silent at epoch 4, making the missing ACK permanently undeliverable and leaving the remote endpoint live indefinitely (e⋆=⊥). With one-bucket linger (L=1), the closing endpoint continues retransmitting FIN+ACK through the next close bucket, resolving all one-sided ACK-loss scenarios in Table VI within epochs 8–12 across all six tested drop counts.
Naïve composition of two unidirectional FEPs leaks private half-close events: when A half-closes after epoch 2 while B's response continues through epoch 6, the zero output in the A→B direction exposes A's private state even though all transmitted bytes appear uniformly random. This attack was confirmed empirically — naive composition leaked in 3/3 close-witness trials versus 0/3 for BiFEP.
None of the six surveyed deployed protocols — TLS 1.3, QUIC v1, WireGuard, Shadowsocks 2022, obfs4, and Tor — provides the full set of BiFEP security properties (exact shaping, delivery, protocol-state integrity, private half-close, and cross-direction isolation) at the specification level.