All of the exposure vectors described here are in effect RIGHT NOW and have been since 2015, when FTC authority over this was killed.
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.
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.
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.
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/named docker image. However with DPI; it's still subject to snoop.
Correct. I recommended the use of DNSCrypt first specifically for this reason.
DNSSEC alone primarily helps prevent DNS spoofing, phishing, and MITM attacks. All useful, but DNSCrypt gives you encrypted DNS queries. Maybe I should have clarified this more.
DNSSEC doesn't prevent DNS spoofing attacks, at least not the kind that occur in the real world. DNSSEC is a server-to-server protocol. From client to server (like with the requests from your browser to your ISP's DNS server, or to Google's DNS server, or whatever you use), there is no cryptography whatsoever protecting the requests. Just a single bit in the header, saying that someone else did the cryptography for you.
7 comments
[ 2.8 ms ] story [ 26.5 ms ] threadThe 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.
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.
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.
DNSSEC alone primarily helps prevent DNS spoofing, phishing, and MITM attacks. All useful, but DNSCrypt gives you encrypted DNS queries. Maybe I should have clarified this more.