News for hackers. Stuff that matters.
Re:It's Time to Fix HTTPS by kragen on Monday March 28, 2011 @12:26PM (#2378923)
Removing the CNNIC cert is not an option if you actually need to talk to sites that use it. And at this point there are literally hundreds of untrustworthy root CA certs in browsers. Just because I want to talk to some server in Turkey doesn't mean I ought to rely on a Turkish organization to vouch for the identity of Bank of America.

This is not a problem with the protocol, but with the criteria used for trusting a signature.

Re:It's Time to Fix HTTPS by tptacek on Monday March 28, 2011 @12:51PM (#2379017)
I know you're a reasonable guy. But, look: you either trust CNNIC or (like me), you don't. If you can't trust CNNIC, you axe their cert and click through to make persistent exceptions to the sites that need that cert.

At the end of the day, we're talking about a very simple UI problem. Yes, our notion of "trust" is broken. But it's broken in large part because nobody has put any effort into communicating to end-users enough information to enable them to make informed decisions. Then, after putting no effort into the problem, we look at and say "you're asking my mom to understand X.509 CNs!", as if that was the extent of what engineering could bring to bear against this problem.

Then we throw up our hands and say "let's make a simpler protocol; who cares if predictably and reliably allows middlemen to hijack our connections, at least we won't have to explain X.509 to our moms".

Can you blame me for being a bit cynical about this?