TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

What you’re revealing to your ISP, why a VPN isn’t enough and ways to protect it

13 pointsby xvolterabout 8 years ago

3 comments

DrScumpabout 8 years ago
All of the exposure vectors described here are in effect RIGHT NOW and have been since 2015, when FTC authority over this was killed.<p>The rule that the Obama administration created (just last December!) that restores some (not all) elements of privacy DOES NOT TAKE EFFECT UNTIL DECEMBER 2 2017 at the earliest. All of the privacy exposures detailed here are CURRENTLY LEGAL and have been for almost 2 years already and, if the Obama rule goes unchanged, would continue through December at least.<p>What this bill actually does is codify the current rule as statute law, meaning that the current and future administrations can’t change this stuff by simple fiat rule change — a passed and signed bill would be necessary.<p>What privacy activists should be demanding is that a statute enforce privacy across all service providers and major content distributors, including Amazon, Hulu, Netflix, etc.
iAm25626about 8 years ago
DNSSEC does not help in the privacy regards. It does not prevent ISP from seeing what domain name you lookup. Running your own DNS server is relative simple: there is a bind&#x2F;named docker image. However with DPI; it&#x27;s still subject to snoop.
评论 #14000448 未加载
woodandsteelabout 8 years ago
I am wondering what people think of cliqz as a solution to these problems.