3 ms·
http://www.jmarshall.com/tools/cgiproxy/ http://www.jmarshall.com/tools/cgiproxy/ Install that on your own server behind Basic Auth. Then it just looks like no
by mike-cardwell 11y ago
http://www.jmarshall.com/tools/cgiproxy/ http://www.jmarshall.com/tools/cgiproxy/
Install that on your own server behind Basic Auth. Then it just looks like normal HTTPS traffic to any sniffer. Because that's exactly what it is.
- aexaey 11y agoThere is an article[1] about finding out what location at google maps user is looking at, based on observing TLS packets and nothing else. If task at hand is to match encrypted connection to a smaller number of alternative (say identify accesses to popular place, like gmail/facebook login page, etc), same technique of observing packet size distribution over time should probably work quite reliably, and cgiproxy will do nothing to hide it. [1] http://www.ioactive.com/pdfs/SSLTrafficAnalysisOnGoogleMaps.pdf http://www.ioactive.com/pdfs/SSLTrafficAnalysisOnGoogleMaps....
- mike-cardwell 11y agoInteresting. CGIProxy could be easily modified to add random padding to the HTML or headers of responses. Probably a couple of lines of Perl.
- JoshTriplett 11y agoYou don't necessarily want random padding; you really want every single packet exactly the same size, potentially with dummy data transmitted to mask data rate as well.
- gtank 11y agoThere's a lot more to defeating traffic analysis than random padding: http://freehaven.net/anonbib/cache/oakland2012-peekaboo.pdf http://freehaven.net/anonbib/cache/oakland2012-peekaboo.pdf