57% accuracy? How about 100% on HTTPS over TCP!
Let me make sure I have this right: You can use QUIC fingerprinting to "infer" which websites a target is accessing, with 57% accuracy? Big deal... I can identify the website a target is accessing with 100% accuracy on HTTPS over TCP, because the domain name is printed at the head of the HTTPS connection in plain text! The reason it's there is so that the software on a shared hosting server knows which site to route the incoming connection to. I have been successfully using this for years to detect streaming video traffic over HTTPS using an L7 filter so it can be prioritized with QoS.
----------35.244.247.133:443 outgoing HTTPS data dump----------
..C-.3.I.$h....Q... 8.:.U..>.. ..p.P9T....gK.*.((..%z..N_.SY.....+./.....,.0.
. ........./.5........#.!...incoming.telemetry.mozilla.org..........
----------172.217.7.238:443 outgoing HTTPS data dump----------
............].....{..=.%...&2...'....n.5..T )..m.x......nAAg...Ry0*..<.7.Z..$.......+./.....,.0
....../.5.......www.youtube.com.................................#.........h2.http/1.1...
---------------------------
See?
Biting the hand that feeds IT
