"Steven M. Bellovin" <[EMAIL PROTECTED]> writes:
> > Now, this does require that the CAs that your browser trusts follow
> > the Common Name=domain name convention, but that's just a special
> > case of trusting your CAs.
>
> The attacker could also present a certficate from a fake CA with an
> appropriate name -- say, "Netscape Security Services", or something that
> plays on the site name they're trying to impersonate -- "Amazon.Com Encryption
> Certification Center" if someone is trying to reach Amazon.com or some such.
Right. In which case Netscape brings up a different dialog which
says that the server certificate is signed by an unrecognized
CA. Again, you can proceed, but it's not like it's automatic.
I'm fairly sure that IE refuses to connect at all.
-Ekr
--
[Eric Rescorla [EMAIL PROTECTED]]
PureTLS - free SSLv3/TLS software for Java
http://www.rtfm.com/puretls/
