To view parent comment, click here.
To read all comments associated with this story, please click here.
Laurence,
"Encrypting your traffic would only hide the content of your traffic, but that data isn't really of interest anyway."
Really? The DPI contents reveals specific search terms, the videos you watch, etc. This is far more personal than knowing which IPs you've connected to. It's the difference between knowing you've connected to ebay, or knowing exactly which products you've been browsing (*).
* Not that I know what ATT & Verizon are actually doing with the data, but there's no doubt the URL/contents can reveal much more about you than the IPs do.
"However, what you can do is run a proxy (VPN, SSH tunnel or even just a straight up web proxy). At least then all of your traffic appears to be going to the same destination (the proxy) and thus their records of you are worthless."
Yes, onion routing tunnels like tor are probably the best defence against ISP tracking today & in the future.
http://www.torproject.org/
A side benefit is that it can be used to work around censorship as well.
Another thing to consider is that one's browser may be "leaky" regardless of the transport encryption. There is a chromium fork designed to strip out identifying bits from packets sent to google.
http://www.srware.net/en/software_srware_iron_chrome_vs_iron.php
Really? The DPI contents reveals specific search terms, the videos you watch, etc. This is far more personal than knowing which IPs you've connected to.
It's the difference between knowing you've connected to ebay, or knowing exactly which products you've been browsing (*).
* Not that I know what ATT & Verizon are actually doing with the data, but there's no doubt the URL/contents can reveal much more about you than the IPs do.
Ahh yes, good point. I forgot that URIs and query strings are sent in the HTTP headers *facepalm*
Another thing to consider is that one's browser may be "leaky" regardless of the transport encryption. There is a chromium fork designed to strip out identifying bits from packets sent to google.
http://www.srware.net/en/software_srware_iron_chrome_vs_iron.php
Don't run Iron, it's a scam:
http://insanitybit.wordpress.com/2012/06/23/srware-iron-browser-a-r...
Nope. What you searched for and what pages you visited is also interesting. The fact that you connected to one of the servers of BBC falls under a lot of categories - news, sports, entertainment, weather and a lot more. Or take visiting any of Google's services - there is known difference only with regard to GMail, while most other services have been moved under the www.google.com domain(ex. https://www.google.com/calendar/ is indistinguishable from https://www.google.com/search?q=test)





Member since:
2007-03-26
Encrypting your traffic would only hide the content of your traffic, but that data isn't really of interest anyway. It's who connected to where, when the connection was made and from where. You cannot encrypt that data as you have to go via your ISP / cell carrier.
However, what you can do is run a proxy (VPN, SSH tunnel or even just a straight up web proxy). At least then all of your traffic appears to be going to the same destination (the proxy) and thus their records of you are worthless.