News for hackers. Stuff that matters.
Re:Adam Langley's Pond: Secure Async Messaging by 9h1d9j809s on Sunday July 14, 2013 @02:49AM (#6040179)
Why? Because DNSSEC can be attacked by the DNS root?

It seemed to be our best attempt to get SSL for every website. CA-based certificates just won't cut it.

Re:Adam Langley's Pond: Secure Async Messaging by tptacek on Sunday July 14, 2013 @10:40AM (#6040964)
Because replacing a PKI run by companies that the NSA can coerce with a PKI run by the US Government doesn't seem like a good plan? That, along with the litany of reasons why DNSSEC is a terrible design; that it doesn't secure queries from stub resolvers where the need is greatest; that it publishes internal zone names; that it breaks the resolver API and will inevitably create outages; I can go on.

(I doubt this is what's held up DANE; rather, the unreliability of DNS compared to hyper-optimized HTTPS/TLS connections is the issue there; browser vendors care about milliseconds.)