Forging the TLS handshake surface (JA3/JA3S fingerprint, certificate, ALPN, HTTP/2 negotiation) requires only minutes via malleable profile configuration, while forging flow-behavior features (inter-arrival timing, packet-size distribution, volume statistics) requires sleep/jitter tuning and cover traffic but remains feasible. The paper explicitly rejects the common assumption that flow behavior cannot be forged.

Adding nine beacon descriptors (inter-arrival-time moments, FFT peak period and power, flow count per endpoint triple, idle ratio) to the flow-statistics view improves Random Forest F1 from 0.747 to 0.856 (+0.109) — one order of magnitude larger than any multi-view fusion gain (+0.022). However, the top-weighted feature beacon_n_flows correlates with capture length (Spearman ρ = 0.718) and its single-feature ROC-AUC varies from 0.173 to 0.977 across folds, indicating it partly reflects a collection artifact rather than real beacon periodicity.

§V-C evaluation

Under simultaneous adversarial forgery of both the TLS handshake fingerprint surface and the flow-behavior surface, all multi-view fusion configurations collapse to approximately 0.07 F1 — well below the trivial always-positive baseline of 0.711 (Δ = 0.590, cluster-bootstrap p < 0.001 over 2,000 resamples of 62 captures). Clean-condition model ranking does not predict adversarial ranking.

§V-E detection

Computing frequency encoding of JA3, JA3S, and SNI across the entire dataset rather than within each cross-validation fold inflates the TLS-view F1 score by 0.28 — approximately ten times larger than any real detection effect measured in the study. When leakage is controlled, the largest genuine multi-view fusion gain over the best single view is only 0.022 F1.

§V-A, Abstract evaluation

The apparent 55.1% positive rate in a 17,577-flow Cobalt Strike corpus is an artifact of counting individual flows rather than endpoints: those flows reduce to only 2,132 independent endpoint groups, where the true positive rate is 4.2%. No endpoint triple carries a mixed label, so flows sharing a destination are not independent observations and standard deviations computed at flow level are artificially small.

§V-A, Table II evaluation

TSG's Context-Based Detector (CBD) evaluates circumvention tool signatures across JA3/JA4 TLS fingerprints, SSL certificate issuer fields, UDP payload length, first-packet byte patterns, server IP ranges, and FQDN matches, often combining multiple conditions with logical AND. Of 29 VPN and circumvention tool signatures logged in the VPN Signature File Update Log (March–November 2024), 21 carry risk level 5 (the maximum), indicating aggressive prioritization of blocking major tools including ExpressVPN, NordVPN, Tor Browser, and Psiphon.

2026-ablove-technical-analysis-geedge §4.1, §4.1.2, Table 3, Table 4 dpitls-fingerprinttraffic-shapeip-blockingsni-blocking

AnyTLS implements a persistent idle-session pool with configurable parameters: idle_session_check_interval (default 30s), idle_session_timeout (default 30s), and min_idle_session (default 5). The client maintains at least 5 pre-established TLS sessions at all times to enable fast connection reuse without a new TLS handshake per request.

2026-anon-anytls-anytls-sing-box-2026 §2.4, §5.3 tls-fingerprinttraffic-shape

Compared to peer protocols, AnyTLS rates 'medium' performance (vs. VLESS 'high', Hysteria2 'very high', TUIC 'high'), uses TCP/TLS transport (vs. UDP/QUIC for Hysteria2 and TUIC), and relies on padding-based obfuscation vs. REALITY/WebSocket (VLESS) or HTTP/3 framing (Hysteria2). Client ecosystem support is currently limited primarily to sing-box, vs. broad cross-client support for VLESS, Trojan, and Hysteria2.

2026-anon-anytls-anytls-sing-box-2026 §1.5, Table 1.5 traffic-shapetls-fingerprint

AnyTLS is a TLS-based proxy protocol maintained by the sing-box team, designed in 2024 and first released in the sing-box dev-next branch. Its core mechanism wraps arbitrary proxy traffic in standard TLS and applies a configurable padding scheme (Padding Scheme) to enhance traffic concealment while maintaining compatibility with standard TLS infrastructure.

2026-anon-anytls-anytls-sing-box-2026 §1.1–1.3 tls-fingerprinttraffic-shapedpi

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.

2026-chen-closing-loop-bidirectional §I (abstract contribution bullet); §VIII-G (referenced protocol comparison) fully-encrypted-detecttraffic-shapetls-fingerprint

Countermeasures against fingerprinting can paradoxically increase a user's identifiability when deployed by a small population: spoofing-introduced attribute inconsistencies and unusual configurations (e.g., Tor Browser's letterboxing applied to an uncommon monitor size) produce a rarer, higher-entropy fingerprint than baseline. This 'information paradox' means that countermeasure effectiveness is a property of the anonymity set size, not of individual tool configuration.

2026-schramm-analyzing-societal-awareness §2.2 tls-fingerprinttraffic-shape