3 ms·
tl;dr - the article is about the susceptibility of SSL protected websites to man-in-the-middle attacks due to the CA trust model being only as strong as the lea
by js2 16y ago
tl;dr - the article is about the susceptibility of SSL protected websites to man-in-the-middle attacks due to the CA trust model being only as strong as the least competent/trustworthy CA that a given browser, well, trusts.
Background: Browsers check for a man-in-the-middle attack by verifying that: a) remote site's certificate is signed by a certificate authority (CA) that the browser trusts; b) the URL matches the common-name attribute (CN) in the site's certificate.
So, for an attacker to get around this check, they need to: a) forge/spoof DNS (relatively easy); b) get a cert signed by a CA the browser trusts with a matching CN of the site to be spoofed (supposed to be relatively hard). (There is also Extended Validation, I won't go into that here.)
Unfortunately, these days, browsers trust _a lot_ of CA's, either directly or via chained certificates. Some of these chained certificates may be surprising to you.
https://www.eff.org/observatory https://www.eff.org/observatory
- tptacek 16y agoThe good news is that this isn't a problem with the SSL protocol so much as it is a problem with how the CA's and browser vendors have decided to configure SSL. Which means you can fix a lot of this by removing certs from your browser configuration.