Tag Info

Hot answers tagged

3

There is no risk of compromising the private key, because you send only the CSR which contains the public, but not the private key. But, using a CA is in effect a trust delegation, e.g. people trust your certificate because they (or the browser) trusts the CA which signed the certificate. Once they notice, that the CA is no longer trustworthy (like DigiNotar ...


1

The risk of using a shifty-looking CA is not in the certificate enrollment process: as long as you generate the key pair yourself and send only the certificate request to the CA (which contains only the public key) and receive the raw certificate in return (not a PKCS#12/PFX archive), then your private key is yours and yours only. The risk, though, is in ...



Only top voted, non community-wiki answers of a minimum length are eligible