FINDING · DETECTION
Across 433,286 endpoints from a 10 Gbps university ISP passive tap, 94% responded with data to at least one of 8 protocol probes (TLS, HTTP, STUN, S7, Modbus, DNS-AXFR, random bytes, empty); all five tested probe-resistant proxies (obfs4, Lampshade, Shadowsocks, MTProto, OSSH) never responded with data to any probe. This single filter reduces the suspect set from 433,286 to ~26,000 endpoints and rules out 94% of ISP-observed hosts as non-proxies with zero false negatives against the tested protocols.
From 2020-frolov-detecting — Detecting Probe-resistant Proxies · §V, Table III · 2020 · Network and Distributed System Security
Implications
- Sending a syntactically plausible error response (e.g., a TLS Alert to a ClientHello) to at least one probe type would defeat this filtering step — but the response must be faithful enough to avoid committing the proxy to a protocol it cannot correctly speak.
- Proxy designers must test non-response behavior against realistic ISP traffic distributions, not just controlled lab datasets, since the 94% elimination rate is vantage-point dependent.
Tags
Extracted by claude-sonnet-4-6 — review before relying.