A CA (Certification Authority) is a trusted third party that vouches for the identity of individuals and organizations. Essentially the certificate authorities maintain a large database of public keys which are distributed as requested. For instance, Godaddy, DigiCert, Verisign etc are popular CAs.
A Certificate Request is used to obtain a CA signed Server Certificate or Client Certificate from a Certification Authority.
A Server Certificate is digital certificate used to identify the server to clients when they connect. The public and private keys associated with the server certificate are also used to encrypt the SSL session key information.
A Client Certificate is a digital certificate used to identify individuals when they connect to an SSL server.
Self-Signed Server Certificates are as cryptographically secure as CA signed certificates but are generally not "trusted" by client programs (e.g. browsers).
A Signing Certificate is used to digitally sign a client or server certificate during the certificate generation process. It is part of the certificate chain.
A Root Certificate is the starting certificate in a certificate hierarchy. All certificates contain information tracing their origin back to a Root Certificate. A Trusted Root Certificate is one where the root certificate is known to the requester. The Trusted Root Certificate must be installed at the client when authenticating a Server Certificate. A Trusted Root Certificate must be installed at the server when authenticating a Client Certificate. (See Mutual TLS authentication)
A Certificate Private Key is used to decrypt messages encrypted using the Certificate Public Key contained in a digital certificate. The Private Key is generally password protected using the Private Key Password (passphrase) to prevent unauthorized use of the Private Key. If the Private Key Password is compromised, the Certificate must be revoked and a new one generated.
How does the client (e.g. browser) know when to trust an SSL certificate?
The connection is trusted if:
- The root certificate for your website matches the pre-installed root certificate in the browser
- None of the certificates in the chain on the server are invalid, expired or revoked.
- The domain name in your certificate matches the domain name in the URL.
No comments:
Post a Comment