3 ms·
>his website is suddenly unavailable to the rest of the city. Lots of people have been concerned about censorship when it comes to net neutrality. Not sure why
by jchw 9y ago
>his website is suddenly unavailable to the rest of the city.
Lots of people have been concerned about censorship when it comes to net neutrality. Not sure why the response is that we want legal protection instead of technical. All of the major vendors of devices that access the internet are pro net-neutrality. Can't we get censorship-resistant, privacy aware DNS resolution at the very least? Maybe not exactly this, but something like this would be nice:
https://developers.google.com/speed/public-dns/docs/dns-over-https https://developers.google.com/speed/public-dns/docs/dns-over...
I think realistically protecting DNS responses would be enough. Even a relatively advanced adversary would have trouble blocking your access to specific sites that way. Can you block a specific CloudFlare-protected site, or specific Twitter accounts? Not really.
AFAIK, the bits you can do with DPI aren't cheap. Only adversaries with reasonably deep pockets can apply.
(To be clear: referring to things like sniffing SNI on TLS connections.)
- Godel_unicode 9y agoWhy do you think DPI isn't cheap? You're aware you can use Snort to drop packets based on SNI at 10gb+ with commodity servers, yes?