5 ms·
Why the browsers must change their old SSL security (?) model
Cites a paper which highlights flaws and threats in the Certificate Authority model and proposes incremental improvements.
- pyre 17y agoChromium didn't like the site's SSL cert (presumably self-signed, the warning page is light on the details, or I just missed a link to more detail).
- epochwolf 17y agoSafari 4 didn't like it either. It looks like a self-signed to me.
- devinj 17y agoFirefox didn't either. I assumed it was a deliberate joke.
- schammy 17y agoHeh, I thought the same thing :)
- wrs 17y agoIt's from CACert (http://www.cacert.org/ http://www.cacert.org/). In Chrome, click on the caution symbol on the right of the address bar to see the cert info. Since his point is that you shouldn't trust the browser to decide whether to trust the CA, it sort of makes sense that he's on CACert...
- fexl 17y agoPrecisely. He did that on purpose, and I remember him saying so at the time. I trusted CACert a long time ago so I forgot all about it. Otherwise I would have posted the http link to avoid the fuss.
- bengtan 17y agoJust use http ... http://financialcryptography.com/mt/archives/001232.html http://financialcryptography.com/mt/archives/001232.html works for me.
- deleted 17y ago[deleted]
- bensummers 17y agoWhen you use an extended validation certificate, I think most browsers make it very easy to see the CA.