News for hackers. Stuff that matters.
Re:Convergence, distributed, secure strategy replacing certi... by IgorPartola on Tuesday September 06, 2011 @11:31AM (#2965925)
Isn't a better long-term solution to simply have DNSSEC distribute your site's public key? The idea that I have to buy a domain name and an SSL certificate is silly. For extended validation, what should be verified is your public key, not your domain. So if the public key is also signed by a number of CAs, it is considered valid.
Re:Convergence, distributed, secure strategy replacing certi... by itsnotvalid on Tuesday September 06, 2011 @03:32PM (#2966922)
This thing is as old as DEFCON 2011 (see http://blog.thoughtcrime.org/ssl-and-the-future-of-authentic...) but in view of current events of certificate trustworthiness, there is quite a chance for anything that can successfully replace the approach of trusting CAs.

Please view this blog entry (from the core author of convergence.io) to get the idea of also why DNSSEC is not a good approach (he had put it in the way that it's worse than CAs.)

Re:Convergence, distributed, secure strategy replacing certi... by dmm on Tuesday September 06, 2011 @01:21PM (#2966342)
But how do I know which DNS servers to trust?
Re:Convergence, distributed, secure strategy replacing certi... by kogir on Tuesday September 06, 2011 @03:13PM (#2966832)
The ones with signatures that check out. That's the SEC part of DNSSEC. The root key(s) are published and you can verify authenticity all the way down.