verify.pod 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413
  1. =pod
  2. =head1 NAME
  3. verify - Utility to verify certificates.
  4. =head1 SYNOPSIS
  5. B<openssl> B<verify>
  6. [B<-CAfile file>]
  7. [B<-CApath directory>]
  8. [B<-attime timestamp>]
  9. [B<-check_ss_sig>]
  10. [B<-crl_check>]
  11. [B<-crl_check_all>]
  12. [B<-explicit_policy>]
  13. [B<-help>]
  14. [B<-ignore_critical>]
  15. [B<-inhibit_any>]
  16. [B<-inhibit_map>]
  17. [B<-issuer_checks>]
  18. [B<-policy arg>]
  19. [B<-policy_check>]
  20. [B<-policy_print>]
  21. [B<-purpose purpose>]
  22. [B<-untrusted file>]
  23. [B<-use_deltas>]
  24. [B<-verbose>]
  25. [B<-verify_depth num>]
  26. [B<-x509_strict>]
  27. [B<->]
  28. [certificates]
  29. =head1 DESCRIPTION
  30. The B<verify> command verifies certificate chains.
  31. =head1 COMMAND OPTIONS
  32. =over 4
  33. =item B<-CAfile file>
  34. A file of trusted certificates. The file should contain multiple certificates
  35. in PEM format concatenated together.
  36. =item B<-CApath directory>
  37. A directory of trusted certificates. The certificates should have names
  38. of the form: hash.0 or have symbolic links to them of this
  39. form ("hash" is the hashed certificate subject name: see the B<-hash> option
  40. of the B<x509> utility). Under Unix the B<c_rehash> script will automatically
  41. create symbolic links to a directory of certificates.
  42. =item B<-attime timestamp>
  43. Perform validation checks using time specified by B<timestamp> and not
  44. current system time. B<timestamp> is the number of seconds since
  45. 01.01.1970 (UNIX time).
  46. =item B<-check_ss_sig>
  47. Verify the signature on the self-signed root CA. This is disabled by default
  48. because it doesn't add any security.
  49. =item B<-crl_check>
  50. Checks end entity certificate validity by attempting to look up a valid CRL.
  51. If a valid CRL cannot be found an error occurs.
  52. =item B<-crl_check_all>
  53. Checks the validity of B<all> certificates in the chain by attempting
  54. to look up valid CRLs.
  55. =item B<-explicit_policy>
  56. Set policy variable require-explicit-policy (see RFC5280).
  57. =item B<-help>
  58. Print out a usage message.
  59. =item B<-ignore_critical>
  60. Normally if an unhandled critical extension is present which is not
  61. supported by OpenSSL the certificate is rejected (as required by RFC5280).
  62. If this option is set critical extensions are ignored.
  63. =item B<-inhibit_any>
  64. Set policy variable inhibit-any-policy (see RFC5280).
  65. =item B<-inhibit_map>
  66. Set policy variable inhibit-policy-mapping (see RFC5280).
  67. =item B<-issuer_checks>
  68. Print out diagnostics relating to searches for the issuer certificate of the
  69. current certificate. This shows why each candidate issuer certificate was
  70. rejected. The presence of rejection messages does not itself imply that
  71. anything is wrong; during the normal verification process, several
  72. rejections may take place.
  73. =item B<-policy arg>
  74. Enable policy processing and add B<arg> to the user-initial-policy-set (see
  75. RFC5280). The policy B<arg> can be an object name an OID in numeric form.
  76. This argument can appear more than once.
  77. =item B<-policy_check>
  78. Enables certificate policy processing.
  79. =item B<-policy_print>
  80. Print out diagnostics related to policy processing.
  81. =item B<-purpose purpose>
  82. The intended use for the certificate. If this option is not specified,
  83. B<verify> will not consider certificate purpose during chain verification.
  84. Currently accepted uses are B<sslclient>, B<sslserver>, B<nssslserver>,
  85. B<smimesign>, B<smimeencrypt>. See the B<VERIFY OPERATION> section for more
  86. information.
  87. =item B<-untrusted file>
  88. A file of untrusted certificates. The file should contain multiple certificates
  89. in PEM format concatenated together.
  90. =item B<-use_deltas>
  91. Enable support for delta CRLs.
  92. =item B<-verbose>
  93. Print extra information about the operations being performed.
  94. =item B<-verify_depth num>
  95. Limit the maximum depth of the certificate chain to B<num> certificates.
  96. =item B<-x509_strict>
  97. For strict X.509 compliance, disable non-compliant workarounds for broken
  98. certificates.
  99. =item B<->
  100. Indicates the last option. All arguments following this are assumed to be
  101. certificate files. This is useful if the first certificate filename begins
  102. with a B<->.
  103. =item B<certificates>
  104. One or more certificates to verify. If no certificates are given, B<verify>
  105. will attempt to read a certificate from standard input. Certificates must be
  106. in PEM format.
  107. =back
  108. =head1 VERIFY OPERATION
  109. The B<verify> program uses the same functions as the internal SSL and S/MIME
  110. verification, therefore this description applies to these verify operations
  111. too.
  112. There is one crucial difference between the verify operations performed
  113. by the B<verify> program: wherever possible an attempt is made to continue
  114. after an error whereas normally the verify operation would halt on the
  115. first error. This allows all the problems with a certificate chain to be
  116. determined.
  117. The verify operation consists of a number of separate steps.
  118. Firstly a certificate chain is built up starting from the supplied certificate
  119. and ending in the root CA. It is an error if the whole chain cannot be built
  120. up. The chain is built up by looking up the issuers certificate of the current
  121. certificate. If a certificate is found which is its own issuer it is assumed
  122. to be the root CA.
  123. The process of 'looking up the issuers certificate' itself involves a number
  124. of steps. In versions of OpenSSL before 0.9.5a the first certificate whose
  125. subject name matched the issuer of the current certificate was assumed to be
  126. the issuers certificate. In OpenSSL 0.9.6 and later all certificates
  127. whose subject name matches the issuer name of the current certificate are
  128. subject to further tests. The relevant authority key identifier components
  129. of the current certificate (if present) must match the subject key identifier
  130. (if present) and issuer and serial number of the candidate issuer, in addition
  131. the keyUsage extension of the candidate issuer (if present) must permit
  132. certificate signing.
  133. The lookup first looks in the list of untrusted certificates and if no match
  134. is found the remaining lookups are from the trusted certificates. The root CA
  135. is always looked up in the trusted certificate list: if the certificate to
  136. verify is a root certificate then an exact match must be found in the trusted
  137. list.
  138. The second operation is to check every untrusted certificate's extensions for
  139. consistency with the supplied purpose. If the B<-purpose> option is not included
  140. then no checks are done. The supplied or "leaf" certificate must have extensions
  141. compatible with the supplied purpose and all other certificates must also be valid
  142. CA certificates. The precise extensions required are described in more detail in
  143. the B<CERTIFICATE EXTENSIONS> section of the B<x509> utility.
  144. The third operation is to check the trust settings on the root CA. The root
  145. CA should be trusted for the supplied purpose. For compatibility with previous
  146. versions of SSLeay and OpenSSL a certificate with no trust settings is considered
  147. to be valid for all purposes.
  148. The final operation is to check the validity of the certificate chain. The validity
  149. period is checked against the current system time and the notBefore and notAfter
  150. dates in the certificate. The certificate signatures are also checked at this
  151. point.
  152. If all operations complete successfully then certificate is considered valid. If
  153. any operation fails then the certificate is not valid.
  154. =head1 DIAGNOSTICS
  155. When a verify operation fails the output messages can be somewhat cryptic. The
  156. general form of the error message is:
  157. server.pem: /C=AU/ST=Queensland/O=CryptSoft Pty Ltd/CN=Test CA (1024 bit)
  158. error 24 at 1 depth lookup:invalid CA certificate
  159. The first line contains the name of the certificate being verified followed by
  160. the subject name of the certificate. The second line contains the error number
  161. and the depth. The depth is number of the certificate being verified when a
  162. problem was detected starting with zero for the certificate being verified itself
  163. then 1 for the CA that signed the certificate and so on. Finally a text version
  164. of the error number is presented.
  165. An exhaustive list of the error codes and messages is shown below, this also
  166. includes the name of the error code as defined in the header file x509_vfy.h
  167. Some of the error codes are defined but never returned: these are described
  168. as "unused".
  169. =over 4
  170. =item B<0 X509_V_OK: ok>
  171. the operation was successful.
  172. =item B<2 X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT: unable to get issuer certificate>
  173. the issuer certificate of a looked up certificate could not be found. This
  174. normally means the list of trusted certificates is not complete.
  175. =item B<3 X509_V_ERR_UNABLE_TO_GET_CRL: unable to get certificate CRL>
  176. the CRL of a certificate could not be found.
  177. =item B<4 X509_V_ERR_UNABLE_TO_DECRYPT_CERT_SIGNATURE: unable to decrypt certificate's signature>
  178. the certificate signature could not be decrypted. This means that the actual signature value
  179. could not be determined rather than it not matching the expected value, this is only
  180. meaningful for RSA keys.
  181. =item B<5 X509_V_ERR_UNABLE_TO_DECRYPT_CRL_SIGNATURE: unable to decrypt CRL's signature>
  182. the CRL signature could not be decrypted: this means that the actual signature value
  183. could not be determined rather than it not matching the expected value. Unused.
  184. =item B<6 X509_V_ERR_UNABLE_TO_DECODE_ISSUER_PUBLIC_KEY: unable to decode issuer public key>
  185. the public key in the certificate SubjectPublicKeyInfo could not be read.
  186. =item B<7 X509_V_ERR_CERT_SIGNATURE_FAILURE: certificate signature failure>
  187. the signature of the certificate is invalid.
  188. =item B<8 X509_V_ERR_CRL_SIGNATURE_FAILURE: CRL signature failure>
  189. the signature of the certificate is invalid.
  190. =item B<9 X509_V_ERR_CERT_NOT_YET_VALID: certificate is not yet valid>
  191. the certificate is not yet valid: the notBefore date is after the current time.
  192. =item B<10 X509_V_ERR_CERT_HAS_EXPIRED: certificate has expired>
  193. the certificate has expired: that is the notAfter date is before the current time.
  194. =item B<11 X509_V_ERR_CRL_NOT_YET_VALID: CRL is not yet valid>
  195. the CRL is not yet valid.
  196. =item B<12 X509_V_ERR_CRL_HAS_EXPIRED: CRL has expired>
  197. the CRL has expired.
  198. =item B<13 X509_V_ERR_ERROR_IN_CERT_NOT_BEFORE_FIELD: format error in certificate's notBefore field>
  199. the certificate notBefore field contains an invalid time.
  200. =item B<14 X509_V_ERR_ERROR_IN_CERT_NOT_AFTER_FIELD: format error in certificate's notAfter field>
  201. the certificate notAfter field contains an invalid time.
  202. =item B<15 X509_V_ERR_ERROR_IN_CRL_LAST_UPDATE_FIELD: format error in CRL's lastUpdate field>
  203. the CRL lastUpdate field contains an invalid time.
  204. =item B<16 X509_V_ERR_ERROR_IN_CRL_NEXT_UPDATE_FIELD: format error in CRL's nextUpdate field>
  205. the CRL nextUpdate field contains an invalid time.
  206. =item B<17 X509_V_ERR_OUT_OF_MEM: out of memory>
  207. an error occurred trying to allocate memory. This should never happen.
  208. =item B<18 X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT: self signed certificate>
  209. the passed certificate is self signed and the same certificate cannot be found in the list of
  210. trusted certificates.
  211. =item B<19 X509_V_ERR_SELF_SIGNED_CERT_IN_CHAIN: self signed certificate in certificate chain>
  212. the certificate chain could be built up using the untrusted certificates but the root could not
  213. be found locally.
  214. =item B<20 X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT_LOCALLY: unable to get local issuer certificate>
  215. the issuer certificate could not be found: this occurs if the issuer
  216. certificate of an untrusted certificate cannot be found.
  217. =item B<21 X509_V_ERR_UNABLE_TO_VERIFY_LEAF_SIGNATURE: unable to verify the first certificate>
  218. no signatures could be verified because the chain contains only one certificate and it is not
  219. self signed.
  220. =item B<22 X509_V_ERR_CERT_CHAIN_TOO_LONG: certificate chain too long>
  221. the certificate chain length is greater than the supplied maximum depth. Unused.
  222. =item B<23 X509_V_ERR_CERT_REVOKED: certificate revoked>
  223. the certificate has been revoked.
  224. =item B<24 X509_V_ERR_INVALID_CA: invalid CA certificate>
  225. a CA certificate is invalid. Either it is not a CA or its extensions are not consistent
  226. with the supplied purpose.
  227. =item B<25 X509_V_ERR_PATH_LENGTH_EXCEEDED: path length constraint exceeded>
  228. the basicConstraints pathlength parameter has been exceeded.
  229. =item B<26 X509_V_ERR_INVALID_PURPOSE: unsupported certificate purpose>
  230. the supplied certificate cannot be used for the specified purpose.
  231. =item B<27 X509_V_ERR_CERT_UNTRUSTED: certificate not trusted>
  232. the root CA is not marked as trusted for the specified purpose.
  233. =item B<28 X509_V_ERR_CERT_REJECTED: certificate rejected>
  234. the root CA is marked to reject the specified purpose.
  235. =item B<29 X509_V_ERR_SUBJECT_ISSUER_MISMATCH: subject issuer mismatch>
  236. the current candidate issuer certificate was rejected because its subject name
  237. did not match the issuer name of the current certificate. Only displayed when
  238. the B<-issuer_checks> option is set.
  239. =item B<30 X509_V_ERR_AKID_SKID_MISMATCH: authority and subject key identifier mismatch>
  240. the current candidate issuer certificate was rejected because its subject key
  241. identifier was present and did not match the authority key identifier current
  242. certificate. Only displayed when the B<-issuer_checks> option is set.
  243. =item B<31 X509_V_ERR_AKID_ISSUER_SERIAL_MISMATCH: authority and issuer serial number mismatch>
  244. the current candidate issuer certificate was rejected because its issuer name
  245. and serial number was present and did not match the authority key identifier
  246. of the current certificate. Only displayed when the B<-issuer_checks> option is set.
  247. =item B<32 X509_V_ERR_KEYUSAGE_NO_CERTSIGN:key usage does not include certificate signing>
  248. the current candidate issuer certificate was rejected because its keyUsage extension
  249. does not permit certificate signing.
  250. =item B<50 X509_V_ERR_APPLICATION_VERIFICATION: application verification failure>
  251. an application specific error. Unused.
  252. =back
  253. =head1 BUGS
  254. Although the issuer checks are a considerable improvement over the old technique they still
  255. suffer from limitations in the underlying X509_LOOKUP API. One consequence of this is that
  256. trusted certificates with matching subject name must either appear in a file (as specified by the
  257. B<-CAfile> option) or a directory (as specified by B<-CApath>). If they occur in both then only
  258. the certificates in the file will be recognised.
  259. Previous versions of OpenSSL assume certificates with matching subject name are identical and
  260. mishandled them.
  261. Previous versions of this documentation swapped the meaning of the
  262. B<X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT> and
  263. B<20 X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT_LOCALLY> error codes.
  264. =head1 SEE ALSO
  265. L<x509(1)|x509(1)>
  266. =cut