4 ms·
As I see it - until there's broad support for Certificate Pinning, your users browsers are going to trust all 700-ish CA Root certs that Chrome/Firefox/Safari/I
by bigiain 13y ago
As I see it - until there's broad support for Certificate Pinning, your users browsers are going to trust all 700-ish CA Root certs that Chrome/Firefox/Safari/IE(/and others) ship with, so your choice of CA doesn't stop Mallory from creating a plausible SSL cert for your domain with her choice of compromised CAs, and have your users believe she's you no matter which CA you carefully chose.
Having said that - if you're being diligent, make sure you generate your own public/private keypair and only send the CSR to the CA to sign your public key.
I noticed recently that StartSSL, although they'll happily accept a CSR, also offer to generate your key pair and give you the private (and public) key. While I understand their desire to make acquiring an SSL cert as easy as possible even for non-technical people (especially since they'll give you a cert for free, so minimising support is clearly critical to their business), the idea of having my private key come from something other than a machine I trust that's completely under my control seems very wrong.