I kind of feel like this could be a perfect opportunity to bring to light some of the weaknesses in the current SSL Cert infrastructure. It sounds like what we

I kind of feel like this could be a perfect opportunity to bring to light some of the weaknesses in the current SSL Cert infrastructure. It sounds like what we need is for the browser to be capable of displaying a list of "favicons" (or something like this, perhaps a favicon encrypted by the domain's private key) from every domain in a domain's certificate chains. And for certificate authorities to allow domain owners to insert their other verified certs in these certificate chains that end up being used. So, for example, let the owner of "DOMAIN1.COM" set up a certificate chain where DOMAIN1.COM is its own certificate authority who signs certs owned by DOMAIN1.COM. This way, when the browser sees the certificate chain it will proceed to verify the chain. So now end users could easily see that DOMAIN2.COM is owned and "vouched for" by DOMAIN1.COM. I don't think FB's claim SHOULD be valid, but given the current state of the art I think it IS valid.