5 ms·
I completely agree with moxie marlinspike but... This article is two years old, and the effort behind the convergence project (http://convergence.io http://con
by NickNameNick 14y ago
I completely agree with moxie marlinspike but...
This article is two years old, and the effort behind the convergence project (http://convergence.io http://convergence.io) seems to have moved on to tack (http://tack.io http://tack.io)
- mistertrotsky 14y agoFuck yeah, I wasn't aware of these projects. I thought the article was exceptionally good and I'm very pleased that there are people taking the initiative to actually do the hard work in search of resolution for the problems detailed. Thank you.
- pi18n 14y agoIt's pretty clear and well-written, so I think its going to be worth reading to explain why the system is wrong for as long as our system is a list of permanently trusted CA's. There's no reason I should be trusting all those CA's to sign for anything on the internet forever.
- kijin 14y agoNo CA is permanently trusted. CA certificates expire like any other SSL certificate, and most of the CA certificates that my browser trusts will expire in about 10 years. In addition, browser vendors like Mozilla routinely make decisions to add and delete CA certificates.
- AnthonyMouse 14y agoI think literally forever is an exaggeration (as it pretty much always is). But the point is that you have to trust them for longer than you would like to, because once they've signed the certificates for a huge chunk of the internet, you can't take them back out without breaking a ton of stuff. Meanwhile as long as they remain trusted they can keep signing new certificates and making it that much harder to ever remove them. The ones that get permanently removed are generally because they've already gone out of business.