Rebound's mole protocol generates a characteristic traffic pattern — a steady stream of long HTTP GET requests followed by 404-style error responses — that may be identifiable via traffic analysis even though the channel is TLS-encrypted; the paper acknowledges this as an unmitigated vulnerability and notes that intermingling with ordinary requests reduces observability but further lowers effective throughput.
From 2015-ellard-rebound — Rebound: Decoy Routing on Asymmetric Routes Via Error Messages
· §VIII-B
· 2015
· Local Computer Networks
Implications
The error-response back-channel is the weakest point of Rebound-style protocols: replace intentionally erroneous GETs with a covert channel that produces traffic indistinguishable from normal browsing (e.g., real resource fetches whose response bodies carry steganographic payloads).
Any mole-style protocol that requires a constant chaff stream should randomise inter-chaff intervals and mix in genuine requests to defeat flow-level pattern classifiers.