OpenSSL VERIFY(1openssl) NNNNAAAAMMMMEEEE
verify - Utility to verify certificates.
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSSooooppppeeeennnnssssssssllll vvvveeeerrrriiiiffffyyyy [---CCCAAAAppppaaaatttthhhh ddddiiiirrrreeeeccccttttoooorrrryyyy] [---CCCAAAAffffiiiilllleeee ffffiiiilllleeee] [---pppuuuurrrrppppoooosssseeee
ppppuuuurrrrppppoooosssseeee] [---uuunnnnttttrrrruuuusssstttteeeedddd ffffiiiilllleeee] [---hhheeeellllpppp] [---iiissssssssuuuueeeerrrr_cccchhhheeeecccckkkkssss]
[---vvveeeerrrrbbbboooosssseeee] [----] [certificates]
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN The vvvveeeerrrriiiiffffyyyy command verifies certificate chains. CCCCOOOOMMMMMMMMAAAANNNNDDDD OOOOPPPPTTTTIIIIOOOONNNNSSSS-CCCCAAAAppppaaaatttthhhh ddddiiiirrrreeeeccccttttoooorrrryyyy
A directory of trusted certificates. The certificates should have names of the form: hash.0 or have symbolic links to them of this form ("hash" is the hashedcertificate subject name: see the ---hhhaaaasssshhhh option of the
xxxx555500009999 utility). Under Unix the cccc_rrrreeeehhhhaaaasssshhhh script will
automatically create symbolic links to a directory of certificates.-CCCCAAAAffffiiiilllleeee ffffiiiilllleeee
A file of trusted certificates. The file should contain multiple certificates in PEM format concatenated together.-uuuunnnnttttrrrruuuusssstttteeeedddd ffffiiiilllleeee
A file of untrusted certificates. The file should contain multiple certificates-ppppuuuurrrrppppoooosssseeee ppppuuuurrrrppppoooosssseeee
the intended use for the certificate. Without this option no chain verification will be done. Currently accepted uses are ssssssssllllcccclllliiiieeeennnntttt, ssssssssllllsssseeeerrrrvvvveeeerrrr, nnnnssssssssssssllllsssseeeerrrrvvvveeeerrrr, ssssmmmmiiiimmmmeeeessssiiiiggggnnnn, ssssmmmmiiiimmmmeeeeeeeennnnccccrrrryyyypppptttt. See the VVVVEEEERRRRIIIIFFFFYYYY OOOOPPPPEEEERRRRAAAATTTTIIIIOOOONNNN section for more information.-hhhheeeellllpppp
prints out a usage message.-vvvveeeerrrrbbbboooosssseeee
print extra information about the operations being performed.-iiiissssssssuuuueeeerrrr_cccchhhheeeecccckkkkssss
print out diagnostics relating to searches for the issuer certificate of the current certificate. This shows why each candidate issuer certificate was rejected. However the presence of rejection messages does not itself imply that anything is wrong: during thenormal verify process several rejections may take place.
23/Feb/2010 Last change: 0.9.8o 1 OpenSSL VERIFY(1openssl)
-cccchhhheeeecccckkkk_ssssssss_ssssiiiigggg
Verify the signature on the self-signed root CA. This is
disabled by default because it doesn't add any security.- marks the last option. All arguments following this are
assumed to be certificate files. This is useful if thefirst certificate filename begins with a ----.
cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeeessssone or more certificates to verify. If no certificate
filenames are included then an attempt is made to read a certificate from standard input. They should all be in PEM format. VVVVEEEERRRRIIIIFFFFYYYY OOOOPPPPEEEERRRRAAAATTTTIIIIOOOONNNN The vvvveeeerrrriiiiffffyyyy program uses the same functions as the internalSSL 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 vvvveeeerrrriiiiffffyyyy program: wherever possible an attempt is made to continue after an errorwhereas 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 the23/Feb/2010 Last change: 0.9.8o 2 OpenSSL VERIFY(1openssl)
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 suppliedpurpose. If the ---pppuuuurrrrppppoooosssseeee 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 CCCCEEEERRRRTTTTIIIIFFFFIIIICCCCAAAATTTTEEEE EEEEXXXXTTTTEEEENNNNSSSSIIIIOOOONNNNSSSS section of the xxxx555500009999 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. DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSSWhen a verify operation fails the output messages can be
somewhat cryptic. The general form of the error message is:server.pem: /C=AU/ST=Queensland/O=CryptSoft Pty Ltd/CN=Test CA (1024 bit) error 24 at 1 depth lookup:invalid CA certificate The first line contains the name of the certificate being verified followed by the subject name of the certificate. The second line contains the error number and the depth. The depth is number of the certificate being verified when a problem was detected starting with zero for the certificate being verified itself then 1 for the CA that signed the certificate and so on. Finally a text version of the error number is presented. An exhaustive list of the error codes and messages is shown below, this also includes the name of the error code as
defined in the header file x509_vfy.h Some of the error
codes are defined but never returned: these are described as "unused".23/Feb/2010 Last change: 0.9.8o 3 OpenSSL VERIFY(1openssl)
0000 XXXX555500009999_VVVV_OOOOKKKK:::: ooookkkk
the operation was successful. cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee2222 XXXX555500009999_VVVV_EEEERRRRRRRR_UUUUNNNNAAAABBBBLLLLEEEE_TTTTOOOO_GGGGEEEETTTT_IIIISSSSSSSSUUUUEEEERRRR_CCCCEEEERRRRTTTT:::: uuuunnnnaaaabbbblllleeee ttttoooo ggggeeeetttt iiiissssssssuuuueeeerrrr
the issuer certificate of a looked up certificate could not be found. This normally means the list of trusted certificates is not complete.3333 XXXX555500009999_VVVV_EEEERRRRRRRR_UUUUNNNNAAAABBBBLLLLEEEE_TTTTOOOO_GGGGEEEETTTT_CCCCRRRRLLLL:::: uuuunnnnaaaabbbblllleeee ttttoooo ggggeeeetttt cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee CCCCRRRRLLLL
the CRL of a certificate could not be found. Unused. cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee''''ssss ssssiiiiggggnnnnaaaattttuuuurrrreeee4444 XXXX555500009999_VVVV_EEEERRRRRRRR_UUUUNNNNAAAABBBBLLLLEEEE_TTTTOOOO_DDDDEEEECCCCRRRRYYYYPPPPTTTT_CCCCEEEERRRRTTTT_SSSSIIIIGGGGNNNNAAAATTTTUUUURRRREEEE:::: uuuunnnnaaaabbbblllleeee ttttoooo ddddeeeeccccrrrryyyypppptttt
the certificate signature could not be decrypted. This means that the actual signature value could not be determined rather than it not matching the expected value, this is only meaningful for RSA keys. CCCCRRRRLLLL''''ssss ssssiiiiggggnnnnaaaattttuuuurrrreeee5555 XXXX555500009999_VVVV_EEEERRRRRRRR_UUUUNNNNAAAABBBBLLLLEEEE_TTTTOOOO_DDDDEEEECCCCRRRRYYYYPPPPTTTT_CCCCRRRRLLLL_SSSSIIIIGGGGNNNNAAAATTTTUUUURRRREEEE:::: uuuunnnnaaaabbbblllleeee ttttoooo ddddeeeeccccrrrryyyypppptttt
the CRL signature could not be decrypted: this means that the actual signature value could not be determined rather than it not matching the expected value. Unused. iiiissssssssuuuueeeerrrr ppppuuuubbbblllliiiicccc kkkkeeeeyyyy6666 XXXX555500009999_VVVV_EEEERRRRRRRR_UUUUNNNNAAAABBBBLLLLEEEE_TTTTOOOO_DDDDEEEECCCCOOOODDDDEEEE_IIIISSSSSSSSUUUUEEEERRRR_PPPPUUUUBBBBLLLLIIIICCCC_KKKKEEEEYYYY:::: uuuunnnnaaaabbbblllleeee ttttoooo ddddeeeeccccooooddddeeee
the public key in the certificate SubjectPublicKeyInfo could not be read. ffffaaaaiiiilllluuuurrrreeee7777 XXXX555500009999_VVVV_EEEERRRRRRRR_CCCCEEEERRRRTTTT_SSSSIIIIGGGGNNNNAAAATTTTUUUURRRREEEE_FFFFAAAAIIIILLLLUUUURRRREEEE:::: cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee ssssiiiiggggnnnnaaaattttuuuurrrreeee
the signature of the certificate is invalid.8888 XXXX555500009999_VVVV_EEEERRRRRRRR_CCCCRRRRLLLL_SSSSIIIIGGGGNNNNAAAATTTTUUUURRRREEEE_FFFFAAAAIIIILLLLUUUURRRREEEE:::: CCCCRRRRLLLL ssssiiiiggggnnnnaaaattttuuuurrrreeee ffffaaaaiiiilllluuuurrrreeee
the signature of the certificate is invalid. Unused.9999 XXXX555500009999_VVVV_EEEERRRRRRRR_CCCCEEEERRRRTTTT_NNNNOOOOTTTT_YYYYEEEETTTT_VVVVAAAALLLLIIIIDDDD:::: cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee iiiissss nnnnooootttt yyyyeeeetttt vvvvaaaalllliiiidddd
the certificate is not yet valid: the notBefore date is after the current time.11110000 XXXX555500009999_VVVV_EEEERRRRRRRR_CCCCEEEERRRRTTTT_HHHHAAAASSSS_EEEEXXXXPPPPIIIIRRRREEEEDDDD:::: cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee hhhhaaaassss eeeexxxxppppiiiirrrreeeedddd
the certificate has expired: that is the notAfter date is before the current time.11111111 XXXX555500009999_VVVV_EEEERRRRRRRR_CCCCRRRRLLLL_NNNNOOOOTTTT_YYYYEEEETTTT_VVVVAAAALLLLIIIIDDDD:::: CCCCRRRRLLLL iiiissss nnnnooootttt yyyyeeeetttt vvvvaaaalllliiiidddd
the CRL is not yet valid. Unused.11112222 XXXX555500009999_VVVV_EEEERRRRRRRR_CCCCRRRRLLLL_HHHHAAAASSSS_EEEEXXXXPPPPIIIIRRRREEEEDDDD:::: CCCCRRRRLLLL hhhhaaaassss eeeexxxxppppiiiirrrreeeedddd
the CRL has expired. Unused.23/Feb/2010 Last change: 0.9.8o 4 OpenSSL VERIFY(1openssl) cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee''''ssss nnnnoooottttBBBBeeeeffffoooorrrreeee ffffiiiieeeelllldddd
11113333 XXXX555500009999_VVVV_EEEERRRRRRRR_EEEERRRRRRRROOOORRRR_IIIINNNN_CCCCEEEERRRRTTTT_NNNNOOOOTTTT_BBBBEEEEFFFFOOOORRRREEEE_FFFFIIIIEEEELLLLDDDD:::: ffffoooorrrrmmmmaaaatttt eeeerrrrrrrroooorrrr iiiinnnn
the certificate notBefore field contains an invalid time. cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee''''ssss nnnnoooottttAAAAfffftttteeeerrrr ffffiiiieeeelllldddd11114444 XXXX555500009999_VVVV_EEEERRRRRRRR_EEEERRRRRRRROOOORRRR_IIIINNNN_CCCCEEEERRRRTTTT_NNNNOOOOTTTT_AAAAFFFFTTTTEEEERRRR_FFFFIIIIEEEELLLLDDDD:::: ffffoooorrrrmmmmaaaatttt eeeerrrrrrrroooorrrr iiiinnnn
the certificate notAfter field contains an invalid time. CCCCRRRRLLLL''''ssss llllaaaassssttttUUUUppppddddaaaatttteeee ffffiiiieeeelllldddd11115555 XXXX555500009999_VVVV_EEEERRRRRRRR_EEEERRRRRRRROOOORRRR_IIIINNNN_CCCCRRRRLLLL_LLLLAAAASSSSTTTT_UUUUPPPPDDDDAAAATTTTEEEE_FFFFIIIIEEEELLLLDDDD:::: ffffoooorrrrmmmmaaaatttt eeeerrrrrrrroooorrrr iiiinnnn
the CRL lastUpdate field contains an invalid time. Unused. CCCCRRRRLLLL''''ssss nnnneeeexxxxttttUUUUppppddddaaaatttteeee ffffiiiieeeelllldddd11116666 XXXX555500009999_VVVV_EEEERRRRRRRR_EEEERRRRRRRROOOORRRR_IIIINNNN_CCCCRRRRLLLL_NNNNEEEEXXXXTTTT_UUUUPPPPDDDDAAAATTTTEEEE_FFFFIIIIEEEELLLLDDDD:::: ffffoooorrrrmmmmaaaatttt eeeerrrrrrrroooorrrr iiiinnnn
the CRL nextUpdate field contains an invalid time. Unused.11117777 XXXX555500009999_VVVV_EEEERRRRRRRR_OOOOUUUUTTTT_OOOOFFFF_MMMMEEEEMMMM:::: oooouuuutttt ooooffff mmmmeeeemmmmoooorrrryyyy
an error occurred trying to allocate memory. This should never happen. cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee11118888 XXXX555500009999_VVVV_EEEERRRRRRRR_DDDDEEEEPPPPTTTTHHHH_ZZZZEEEERRRROOOO_SSSSEEEELLLLFFFF_SSSSIIIIGGGGNNNNEEEEDDDD_CCCCEEEERRRRTTTT:::: sssseeeellllffff ssssiiiiggggnnnneeeedddd
the passed certificate is self signed and the same certificate cannot be found in the list of trusted certificates. iiiinnnn cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee cccchhhhaaaaiiiinnnn11119999 XXXX555500009999_VVVV_EEEERRRRRRRR_SSSSEEEELLLLFFFF_SSSSIIIIGGGGNNNNEEEEDDDD_CCCCEEEERRRRTTTT_IIIINNNN_CCCCHHHHAAAAIIIINNNN:::: sssseeeellllffff ssssiiiiggggnnnneeeedddd cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee
the certificate chain could be built up using the untrusted certificates but the root could not be found locally. llllooooccccaaaallll iiiissssssssuuuueeeerrrr cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee22220000 XXXX555500009999_VVVV_EEEERRRRRRRR_UUUUNNNNAAAABBBBLLLLEEEE_TTTTOOOO_GGGGEEEETTTT_IIIISSSSSSSSUUUUEEEERRRR_CCCCEEEERRRRTTTT_LLLLOOOOCCCCAAAALLLLLLLLYYYY:::: uuuunnnnaaaabbbblllleeee ttttoooo ggggeeeetttt
the issuer certificate could not be found: this occurs if the issuer certificate of an untrusted certificate cannot be found. tttthhhheeee ffffiiiirrrrsssstttt cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee22221111 XXXX555500009999_VVVV_EEEERRRRRRRR_UUUUNNNNAAAABBBBLLLLEEEE_TTTTOOOO_VVVVEEEERRRRIIIIFFFFYYYY_LLLLEEEEAAAAFFFF_SSSSIIIIGGGGNNNNAAAATTTTUUUURRRREEEE:::: uuuunnnnaaaabbbblllleeee ttttoooo vvvveeeerrrriiiiffffyyyy
no signatures could be verified because the chain contains only one certificate and it is not self signed.22222222 XXXX555500009999_VVVV_EEEERRRRRRRR_CCCCEEEERRRRTTTT_CCCCHHHHAAAAIIIINNNN_TTTTOOOOOOOO_LLLLOOOONNNNGGGG:::: cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee cccchhhhaaaaiiiinnnn ttttoooooooo lllloooonnnngggg
the certificate chain length is greater than the supplied maximum depth. Unused.22223333 XXXX555500009999_VVVV_EEEERRRRRRRR_CCCCEEEERRRRTTTT_RRRREEEEVVVVOOOOKKKKEEEEDDDD:::: cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee rrrreeeevvvvooookkkkeeeedddd
the certificate has been revoked. Unused.23/Feb/2010 Last change: 0.9.8o 5 OpenSSL VERIFY(1openssl)
22224444 XXXX555500009999_VVVV_EEEERRRRRRRR_IIIINNNNVVVVAAAALLLLIIIIDDDD_CCCCAAAA:::: iiiinnnnvvvvaaaalllliiiidddd CCCCAAAA cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee
a CA certificate is invalid. Either it is not a CA or its extensions are not consistent with the supplied purpose. eeeexxxxcccceeeeeeeeddddeeeedddd22225555 XXXX555500009999_VVVV_EEEERRRRRRRR_PPPPAAAATTTTHHHH_LLLLEEEENNNNGGGGTTTTHHHH_EEEEXXXXCCCCEEEEEEEEDDDDEEEEDDDD:::: ppppaaaatttthhhh lllleeeennnnggggtttthhhh ccccoooonnnnssssttttrrrraaaaiiiinnnntttt
the basicConstraints pathlength parameter has been exceeded.22226666 XXXX555500009999_VVVV_EEEERRRRRRRR_IIIINNNNVVVVAAAALLLLIIIIDDDD_PPPPUUUURRRRPPPPOOOOSSSSEEEE:::: uuuunnnnssssuuuuppppppppoooorrrrtttteeeedddd cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee ppppuuuurrrrppppoooosssseeee
the supplied certificate cannot be used for the specified purpose.22227777 XXXX555500009999_VVVV_EEEERRRRRRRR_CCCCEEEERRRRTTTT_UUUUNNNNTTTTRRRRUUUUSSSSTTTTEEEEDDDD:::: cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee nnnnooootttt ttttrrrruuuusssstttteeeedddd
the root CA is not marked as trusted for the specified purpose.22228888 XXXX555500009999_VVVV_EEEERRRRRRRR_CCCCEEEERRRRTTTT_RRRREEEEJJJJEEEECCCCTTTTEEEEDDDD:::: cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee rrrreeeejjjjeeeecccctttteeeedddd
the root CA is marked to reject the specified purpose.22229999 XXXX555500009999_VVVV_EEEERRRRRRRR_SSSSUUUUBBBBJJJJEEEECCCCTTTT_IIIISSSSSSSSUUUUEEEERRRR_MMMMIIIISSSSMMMMAAAATTTTCCCCHHHH:::: ssssuuuubbbbjjjjeeeecccctttt iiiissssssssuuuueeeerrrr mmmmiiiissssmmmmaaaattttcccchhhh
the current candidate issuer certificate was rejected because its subject name did not match the issuer name of the current certificate. Only displayed when the---iiissssssssuuuueeeerrrr_cccchhhheeeecccckkkkssss option is set.
iiiiddddeeeennnnttttiiiiffffiiiieeeerrrr mmmmiiiissssmmmmaaaattttcccchhhh33330000 XXXX555500009999_VVVV_EEEERRRRRRRR_AAAAKKKKIIIIDDDD_SSSSKKKKIIIIDDDD_MMMMIIIISSSSMMMMAAAATTTTCCCCHHHH:::: aaaauuuutttthhhhoooorrrriiiittttyyyy aaaannnndddd ssssuuuubbbbjjjjeeeecccctttt kkkkeeeeyyyy
the current candidate issuer certificate was rejected because its subject key identifier was present and did not match the authority key identifier currentcertificate. Only displayed when the ---iiissssssssuuuueeeerrrr_cccchhhheeeecccckkkkssss
option is set. sssseeeerrrriiiiaaaallll nnnnuuuummmmbbbbeeeerrrr mmmmiiiissssmmmmaaaattttcccchhhh33331111 XXXX555500009999_VVVV_EEEERRRRRRRR_AAAAKKKKIIIIDDDD_IIIISSSSSSSSUUUUEEEERRRR_SSSSEEEERRRRIIIIAAAALLLL_MMMMIIIISSSSMMMMAAAATTTTCCCCHHHH:::: aaaauuuutttthhhhoooorrrriiiittttyyyy aaaannnndddd iiiissssssssuuuueeeerrrr
the current candidate issuer certificate was rejected because its issuer name and serial number was present and did not match the authority key identifier of the current certificate. Only displayed when the---iiissssssssuuuueeeerrrr_cccchhhheeeecccckkkkssss option is set.
cccceeeerrrrttttiiiiffffiiiiccccaaaatttteeee ssssiiiiggggnnnniiiinnnngggg33332222 XXXX555500009999_VVVV_EEEERRRRRRRR_KKKKEEEEYYYYUUUUSSSSAAAAGGGGEEEE_NNNNOOOO_CCCCEEEERRRRTTTTSSSSIIIIGGGGNNNN::::kkkkeeeeyyyy uuuussssaaaaggggeeee ddddooooeeeessss nnnnooootttt iiiinnnncccclllluuuuddddeeee
the current candidate issuer certificate was rejected because its keyUsage extension does not permit certificate signing. ffffaaaaiiiilllluuuurrrreeee55550000 XXXX555500009999_VVVV_EEEERRRRRRRR_AAAAPPPPPPPPLLLLIIIICCCCAAAATTTTIIIIOOOONNNN_VVVVEEEERRRRIIIIFFFFIIIICCCCAAAATTTTIIIIOOOONNNN:::: aaaapppppppplllliiiiccccaaaattttiiiioooonnnn vvvveeeerrrriiiiffffiiiiccccaaaattttiiiioooonnnn
an application specific error. Unused.23/Feb/2010 Last change: 0.9.8o 6 OpenSSL VERIFY(1openssl) BBBBUUUUGGGGSSSS Although the issuer checks are a considerably improvement over the old technique they still suffer from limitations in
the underlying X509_LOOKUP API. One consequence of this is
that trusted certificates with matching subject name musteither appear in a file (as specified by the ---CCCAAAAffffiiiilllleeee option)
or a directory (as specified by ---CCCAAAAppppaaaatttthhhh. If they occur in
both then only the certificates in the file will be recognised. Previous versions of OpenSSL assume certificates with matching subject name are identical and mishandled them. Previous versions of this documentation swapped the meaningof the XXXX555500009999_VVVV_EEEERRRRRRRR_UUUUNNNNAAAABBBBLLLLEEEE_TTTTOOOO_GGGGEEEETTTT_IIIISSSSSSSSUUUUEEEERRRR_CCCCEEEERRRRTTTT and 22220000
XXXX555500009999_VVVV_EEEERRRRRRRR_UUUUNNNNAAAABBBBLLLLEEEE_TTTTOOOO_GGGGEEEETTTT_IIIISSSSSSSSUUUUEEEERRRR_CCCCEEEERRRRTTTT_LLLLOOOOCCCCAAAALLLLLLLLYYYY error codes.
SSSSEEEEEEEE AAAALLLLSSSSOOOO x509(1)23/Feb/2010 Last change: 0.9.8o 7 OpenSSL VERIFY(1openssl)
23/Feb/2010 Last change: 0.9.8o 8