News for hackers. Stuff that matters.
Re:Pro-SOPA Comcast just implemented SOPA-incompatible DNSSEC by tedunangst on Wednesday January 11, 2012 @10:50PM (#3454969)
It doesn't matter if the NXDOMAIN is forged or not (or whether forgery is detected or not). It's not like you can unforge and extract the original IP from such a response. Your browser can flash all the red warning lights it wants, you're not going to connect to the naughty site. DNSSEC does absolutely nothing to impede DNS blacklisting.
Re:Pro-SOPA Comcast just implemented SOPA-incompatible DNSSEC by wmf on Wednesday January 11, 2012 @11:58PM (#3455111)
That's never been the issue. When people claim that "SOPA breaks DNSSEC" (note they don't say the reverse) they mean that a SOPA blockage looks the same as a MITM attack from the client's perspective. As I've explained earlier, ISPs can choose to make it look like a DNS server outage instead of an MITM; this might produce fewer misleading errors in the browser. SOPA works fine as written, it just makes DNS debugging harder. "Users running secure applications have a need to distinguish between policy-based failures and failures caused, for example, by the presence of an attack or a hostile network, or else downgrade attacks would likely be prolific." http://www.circleid.com/pdf/PROTECT-IP-Technical-Whitepaper-...