Ask HN: What are good ways to hide metadata from your ISP?
Even with HTTPS, my ISP can still:
A) see the domain names of sites to which I connect
B)the time at which a connection was made
C) the volume of data moving over a connection
So even if I use a VPN, my ISP can still see that I connected to https://vpn.com around the same time https://vpn.com connected to https://embarrasingNSFWsite.ru. They can also see that the data from https://embarassingNSFWsite.ru is pretty similar in size to the data I recieved from my vpn.
So, are there any tools or techniques that can eliminate these inferences, or at least reduce their accuracy?
(
50 comments
| 50 points
| on HN
)
Your ISP is very unlikely to have access to any traffic logging from your VPN endpoint, unless you are using the same ISP for both.
My solution to this has been to spin up a VPN server on Digital Ocean and just route all traffic through that. Bonus: native IPv6 over the VPN.
VPN's like PIA do provide a layer of abstraction; you could save a small amount of money running your VPN NAT on a VPS.
[1] https://github.com/trailofbits/algo
There is a document on the Digital Ocean site about how to do it, though: https://www.digitalocean.com/community/tutorials/how-to-set-...
- It's residential ISPs that are unreasonably tracking metadata, rather than infrastructure providers.
- Even if that no longer applies, it's possible to use a VPN in a friendlier jurisdiction.
- The details of what you are doing are more obfuscated. If you're sharing a VPN, that has obvious benefits. If you use an anonymous VPN, even better.
Ultimately there will always be some data about your internet use available to a determined adversary – it's ultimately just a side-effect of wanting to send data across a network. But I'm personally more interested in opting out of the dragnet-style metadata collection that's being played with in the UK, so keeping my traffic out of sight of my ISP is a benefit.
By virtue of TCP/IP isn't it futile to think you can achieve "true privacy" without something like TOR? (A different protocol with the obfuscation baked in?)
Someone is always going to have logs of your activity, the goal being not giving them "end to end logs" easily.
The logging you have to worry about is the VPN endpoint, hopefully your VPN provider does not keep logs of your activity.
The EFF also has na article on fingerprinting [1] which I believe makes using a vpn moot. if you want anonymity I believe the use of tools like Qubes and Whonix would be good place to start.
[0] https://www.eff.org/pages/tor-and-https [1] https://panopticlick.eff.org/
- Create a program to crawl and store every link provided by some link aggregator (such as HN or Reddit, or both). wget's mirroring and link rewriting is remarkably good at this.
- Create a secondary program to do Google searches on a set of arbitrary phrases (I'm thinking "go through Wikipedia & pick random phrases) and locally store those results as well. You could (carefully) include phrases you're actually interested in.
- Browse the stored data with your internet disconnected.
Of course, this limits your browsing breadth significantly, creates a delay between knowing what you want to view and being able to securely view it, and will frequently eliminate Javascript App style websites; but it's the one way I know which will make snooping on what you are actually viewing much harder.
Also, they may be the ISP of the site, in which case they can see your connection to the VPN and a connection from the same VPN.
You may be describing a reverse proxy, which is not the same thing as a vpn but if it's set up properly it still should mask the metadata of what it connects to.
If it's a very tiny percentage, wouldn't your average VPN user stick out like a sore thumb? I mean if say, authorities were monitoring what was going on, surely a VPN is a strong signal for "extra scrutiny"?
If you're really paranoid, buy a dedicated laptop (with cash, preferably in another town and leave your cellphone at home).
It's worth remembering; 87% of people can be uniquely identified with a zip code, gender, and their birthdate.
Operational security - remaining consistently anonymous - is hard.
https://news.ycombinator.com/item?id=2942967
There are a number of good hits on google on the search "uniquely identify person zip code birthdate"
https://en.wikipedia.org/wiki/Legality_of_piggybacking
Public wifi like someone else mentioned earlier.