OpenSSL Verify Operation Steps
How does the OpenSSL verify operation work? What are the steps used by OpenSSL to verify a certificate?
The OpenSSL verify operation uses the same functions as the internal SSL and S/MIME verification, therefore this description applies to these verify operations too.
There is one crucial difference between the verify operations performed by the verify program: wherever possible an attempt is made to continue after an error whereas normally the verify operation would halt on the first error. This allows all the problems with a certificate chain to be determined.
The verify operation consists of a number of separate steps.
Firstly a certificate chain is built up starting from the supplied certificate and ending in the root CA. It is an error if the whole chain cannot be built up. The chain is built up by looking up the issuers certificate of the current certificate. If a certificate is found which is its own issuer it is assumed to be the root CA.
The process of 'looking up the issuers certificate' itself involves a number of steps. In versions of OpenSSL before 0.9.5a the first certificate whose subject name matched the issuer of the current certificate was assumed to be the issuers certificate. In OpenSSL 0.9.6 and later all certificates whose subject name matches the issuer name of the current certificate are subject to further tests. The relevant authority key identifier components of the current certificate (if present) must match the subject key identifier (if present) and issuer and serial number of the candidate issuer, in addition the keyUsage extension of the candidate issuer (if present) must permit certificate signing.
The lookup first looks in the list of untrusted certificates and if no match is found the remaining lookups are from the trusted certificates. The root CA is always looked up in the trusted certificate list: if the certificate to verify is a root certificate then an exact match must be found in the trusted list.
The second operation is to check every untrusted certificate's extensions for consistency with the supplied purpose. If the -purpose option is not included then no checks are done. The supplied or ``leaf'' certificate must have extensions compatible with the supplied purpose and all other certificates must also be valid CA certificates. The precise extensions required are described in more detail in the CERTIFICATE EXTENSIONS section of the x509 utility.
The third operation is to check the trust settings on the root CA. The root CA should be trusted for the supplied purpose. For compatibility with previous versions of SSLeay and OpenSSL a certificate with no trust settings is considered to be valid for all purposes.
The final operation is to check the validity of the certificate chain. The validity period is checked against the current system time and the notBefore and notAfter dates in the certificate. The certificate signatures are also checked at this point.
If all operations complete successfully then certificate is considered valid. If any operation fails then the certificate is not valid.
2012-07-24, 4128👍, 0💬
What options are supported by the "keytool -gencert" command? Java Keytool can be used to sign a CSR...
How to use the "keytool -genkeypair" command? I want to generate a pair of public key and private ke...
Certificate Summary: Subject: Go Daddy Class 2 Certification Authority Issuer: Go Daddy Class 2 Cert...
How to decode an X.509 certificate and view its content? To help you to decode X.509 certificate and...
What options are supported by the "keytool -printcertreq" command? Java Keytool can be used to print...