1 .\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.28)
4 .\" ========================================================================
5 .de Sp \" Vertical space (when we can't use .PP)
9 .de Vb \" Begin verbatim text
14 .de Ve \" End verbatim text
18 .\" Set up some character translations and predefined strings. \*(-- will
19 .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
20 .\" double quote, and \*(R" will give a right double quote. \*(C+ will
21 .\" give a nicer C++. Capital omega is used to do unbreakable dashes and
22 .\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
23 .\" nothing in troff, for use with C<>.
25 .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
29 . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
30 . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
45 .\" Escape single quotes in literal strings from groff's Unicode transform.
49 .\" If the F register is turned on, we'll generate index entries on stderr for
50 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
51 .\" entries marked with X<> in POD. Of course, you'll have to process the
52 .\" output yourself in some meaningful fashion.
54 .\" Avoid warning from groff about undefined register 'F'.
58 .if \n(.g .if rF .nr rF 1
59 .if (\n(rF:(\n(.g==0)) \{
62 . tm Index:\\$1\t\\n%\t"\\$2"
72 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
73 .\" Fear. Run. Save yourself. No user-serviceable parts.
74 . \" fudge factors for nroff and troff
83 . ds #H ((1u-(\\\\n(.fu%2u))*.13m)
89 . \" simple accents for nroff and troff
99 . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
100 . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
101 . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
102 . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
103 . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
104 . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
106 . \" troff and (daisy-wheel) nroff accents
107 .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
108 .ds 8 \h'\*(#H'\(*b\h'-\*(#H'
109 .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
110 .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
111 .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
112 .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
113 .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
114 .ds ae a\h'-(\w'a'u*4/10)'e
115 .ds Ae A\h'-(\w'A'u*4/10)'E
116 . \" corrections for vroff
117 .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
118 .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
119 . \" for low resolution devices (crt and lpr)
120 .if \n(.H>23 .if \n(.V>19 \
133 .\" ========================================================================
136 .TH VERIFY 1 "2016-09-22" "1.0.1u" "OpenSSL"
137 .\" For nroff, turn off justification. Always turn off hyphenation; it makes
138 .\" way too many mistakes in technical documents.
142 verify \- Utility to verify certificates.
144 .IX Header "SYNOPSIS"
145 \&\fBopenssl\fR \fBverify\fR
146 [\fB\-CApath directory\fR]
147 [\fB\-CAfile file\fR]
148 [\fB\-purpose purpose\fR]
150 [\fB\-ignore_critical\fR]
152 [\fB\-crl_check_all\fR]
153 [\fB\-policy_check\fR]
154 [\fB\-explicit_policy\fR]
155 [\fB\-inhibit_any\fR]
156 [\fB\-inhibit_map\fR]
157 [\fB\-x509_strict\fR]
158 [\fB\-extended_crl\fR]
160 [\fB\-policy_print\fR]
161 [\fB\-no_alt_chains\fR]
162 [\fB\-allow_proxy_certs\fR]
163 [\fB\-untrusted file\fR]
165 [\fB\-issuer_checks\fR]
166 [\fB\-attime timestamp\fR]
171 .IX Header "DESCRIPTION"
172 The \fBverify\fR command verifies certificate chains.
173 .SH "COMMAND OPTIONS"
174 .IX Header "COMMAND OPTIONS"
175 .IP "\fB\-CApath directory\fR" 4
176 .IX Item "-CApath directory"
177 A directory of trusted certificates. The certificates should have names
178 of the form: hash.0 or have symbolic links to them of this
179 form (\*(L"hash\*(R" is the hashed certificate subject name: see the \fB\-hash\fR option
180 of the \fBx509\fR utility). Under Unix the \fBc_rehash\fR script will automatically
181 create symbolic links to a directory of certificates.
182 .IP "\fB\-CAfile file\fR A file of trusted certificates. The file should contain multiple certificates in \s-1PEM\s0 format concatenated together." 4
183 .IX Item "-CAfile file A file of trusted certificates. The file should contain multiple certificates in PEM format concatenated together."
185 .IP "\fB\-untrusted file\fR" 4
186 .IX Item "-untrusted file"
188 A file of untrusted certificates. The file should contain multiple certificates
189 in \s-1PEM\s0 format concatenated together.
190 .IP "\fB\-purpose purpose\fR" 4
191 .IX Item "-purpose purpose"
192 The intended use for the certificate. If this option is not specified,
193 \&\fBverify\fR will not consider certificate purpose during chain verification.
194 Currently accepted uses are \fBsslclient\fR, \fBsslserver\fR, \fBnssslserver\fR,
195 \&\fBsmimesign\fR, \fBsmimeencrypt\fR. See the \fB\s-1VERIFY OPERATION\s0\fR section for more
199 Print out a usage message.
200 .IP "\fB\-verbose\fR" 4
202 Print extra information about the operations being performed.
203 .IP "\fB\-issuer_checks\fR" 4
204 .IX Item "-issuer_checks"
205 Print out diagnostics relating to searches for the issuer certificate of the
206 current certificate. This shows why each candidate issuer certificate was
207 rejected. The presence of rejection messages does not itself imply that
208 anything is wrong; during the normal verification process, several
209 rejections may take place.
210 .IP "\fB\-attime timestamp\fR" 4
211 .IX Item "-attime timestamp"
212 Perform validation checks using time specified by \fBtimestamp\fR and not
213 current system time. \fBtimestamp\fR is the number of seconds since
214 01.01.1970 (\s-1UNIX\s0 time).
215 .IP "\fB\-policy arg\fR" 4
216 .IX Item "-policy arg"
217 Enable policy processing and add \fBarg\fR to the user-initial-policy-set (see
218 \&\s-1RFC5280\s0). The policy \fBarg\fR can be an object name an \s-1OID\s0 in numeric form.
219 This argument can appear more than once.
220 .IP "\fB\-policy_check\fR" 4
221 .IX Item "-policy_check"
222 Enables certificate policy processing.
223 .IP "\fB\-explicit_policy\fR" 4
224 .IX Item "-explicit_policy"
225 Set policy variable require-explicit-policy (see \s-1RFC5280\s0).
226 .IP "\fB\-inhibit_any\fR" 4
227 .IX Item "-inhibit_any"
228 Set policy variable inhibit-any-policy (see \s-1RFC5280\s0).
229 .IP "\fB\-inhibit_map\fR" 4
230 .IX Item "-inhibit_map"
231 Set policy variable inhibit-policy-mapping (see \s-1RFC5280\s0).
232 .IP "\fB\-no_alt_chains\fR" 4
233 .IX Item "-no_alt_chains"
234 When building a certificate chain, if the first certificate chain found is not
235 trusted, then OpenSSL will continue to check to see if an alternative chain can
236 be found that is trusted. With this option that behaviour is suppressed so that
237 only the first chain found is ever used. Using this option will force the
238 behaviour to match that of previous OpenSSL versions.
239 .IP "\fB\-allow_proxy_certs\fR" 4
240 .IX Item "-allow_proxy_certs"
241 Allow the verification of proxy certificates.
242 .IP "\fB\-policy_print\fR" 4
243 .IX Item "-policy_print"
244 Print out diagnostics related to policy processing.
245 .IP "\fB\-crl_check\fR" 4
246 .IX Item "-crl_check"
247 Checks end entity certificate validity by attempting to look up a valid \s-1CRL.\s0
248 If a valid \s-1CRL\s0 cannot be found an error occurs.
249 .IP "\fB\-crl_check_all\fR" 4
250 .IX Item "-crl_check_all"
251 Checks the validity of \fBall\fR certificates in the chain by attempting
252 to look up valid CRLs.
253 .IP "\fB\-ignore_critical\fR" 4
254 .IX Item "-ignore_critical"
255 Normally if an unhandled critical extension is present which is not
256 supported by OpenSSL the certificate is rejected (as required by \s-1RFC5280\s0).
257 If this option is set critical extensions are ignored.
258 .IP "\fB\-x509_strict\fR" 4
259 .IX Item "-x509_strict"
260 For strict X.509 compliance, disable non-compliant workarounds for broken
262 .IP "\fB\-extended_crl\fR" 4
263 .IX Item "-extended_crl"
264 Enable extended \s-1CRL\s0 features such as indirect CRLs and alternate \s-1CRL\s0
266 .IP "\fB\-use_deltas\fR" 4
267 .IX Item "-use_deltas"
268 Enable support for delta CRLs.
269 .IP "\fB\-check_ss_sig\fR" 4
270 .IX Item "-check_ss_sig"
271 Verify the signature on the self-signed root \s-1CA.\s0 This is disabled by default
272 because it doesn't add any security.
275 Indicates the last option. All arguments following this are assumed to be
276 certificate files. This is useful if the first certificate filename begins
278 .IP "\fBcertificates\fR" 4
279 .IX Item "certificates"
280 One or more certificates to verify. If no certificates are given, \fBverify\fR
281 will attempt to read a certificate from standard input. Certificates must be
282 in \s-1PEM\s0 format.
283 .SH "VERIFY OPERATION"
284 .IX Header "VERIFY OPERATION"
285 The \fBverify\fR program uses the same functions as the internal \s-1SSL\s0 and S/MIME
286 verification, therefore this description applies to these verify operations
289 There is one crucial difference between the verify operations performed
290 by the \fBverify\fR program: wherever possible an attempt is made to continue
291 after an error whereas normally the verify operation would halt on the
292 first error. This allows all the problems with a certificate chain to be
295 The verify operation consists of a number of separate steps.
297 Firstly a certificate chain is built up starting from the supplied certificate
298 and ending in the root \s-1CA.\s0 It is an error if the whole chain cannot be built
299 up. The chain is built up by looking up the issuers certificate of the current
300 certificate. If a certificate is found which is its own issuer it is assumed
301 to be the root \s-1CA.\s0
303 The process of 'looking up the issuers certificate' itself involves a number
304 of steps. In versions of OpenSSL before 0.9.5a the first certificate whose
305 subject name matched the issuer of the current certificate was assumed to be
306 the issuers certificate. In OpenSSL 0.9.6 and later all certificates
307 whose subject name matches the issuer name of the current certificate are
308 subject to further tests. The relevant authority key identifier components
309 of the current certificate (if present) must match the subject key identifier
310 (if present) and issuer and serial number of the candidate issuer, in addition
311 the keyUsage extension of the candidate issuer (if present) must permit
314 The lookup first looks in the list of untrusted certificates and if no match
315 is found the remaining lookups are from the trusted certificates. The root \s-1CA\s0
316 is always looked up in the trusted certificate list: if the certificate to
317 verify is a root certificate then an exact match must be found in the trusted
320 The second operation is to check every untrusted certificate's extensions for
321 consistency with the supplied purpose. If the \fB\-purpose\fR option is not included
322 then no checks are done. The supplied or \*(L"leaf\*(R" certificate must have extensions
323 compatible with the supplied purpose and all other certificates must also be valid
324 \&\s-1CA\s0 certificates. The precise extensions required are described in more detail in
325 the \fB\s-1CERTIFICATE EXTENSIONS\s0\fR section of the \fBx509\fR utility.
327 The third operation is to check the trust settings on the root \s-1CA.\s0 The root
328 \&\s-1CA\s0 should be trusted for the supplied purpose. For compatibility with previous
329 versions of SSLeay and OpenSSL a certificate with no trust settings is considered
330 to be valid for all purposes.
332 The final operation is to check the validity of the certificate chain. The validity
333 period is checked against the current system time and the notBefore and notAfter
334 dates in the certificate. The certificate signatures are also checked at this
337 If all operations complete successfully then certificate is considered valid. If
338 any operation fails then the certificate is not valid.
340 .IX Header "DIAGNOSTICS"
341 When a verify operation fails the output messages can be somewhat cryptic. The
342 general form of the error message is:
345 \& server.pem: /C=AU/ST=Queensland/O=CryptSoft Pty Ltd/CN=Test CA (1024 bit)
346 \& error 24 at 1 depth lookup:invalid CA certificate
349 The first line contains the name of the certificate being verified followed by
350 the subject name of the certificate. The second line contains the error number
351 and the depth. The depth is number of the certificate being verified when a
352 problem was detected starting with zero for the certificate being verified itself
353 then 1 for the \s-1CA\s0 that signed the certificate and so on. Finally a text version
354 of the error number is presented.
356 An exhaustive list of the error codes and messages is shown below, this also
357 includes the name of the error code as defined in the header file x509_vfy.h
358 Some of the error codes are defined but never returned: these are described
360 .IP "\fB0 X509_V_OK: ok\fR" 4
361 .IX Item "0 X509_V_OK: ok"
362 the operation was successful.
363 .IP "\fB2 X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT: unable to get issuer certificate\fR" 4
364 .IX Item "2 X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT: unable to get issuer certificate"
365 the issuer certificate of a looked up certificate could not be found. This
366 normally means the list of trusted certificates is not complete.
367 .IP "\fB3 X509_V_ERR_UNABLE_TO_GET_CRL: unable to get certificate \s-1CRL\s0\fR" 4
368 .IX Item "3 X509_V_ERR_UNABLE_TO_GET_CRL: unable to get certificate CRL"
369 the \s-1CRL\s0 of a certificate could not be found.
370 .IP "\fB4 X509_V_ERR_UNABLE_TO_DECRYPT_CERT_SIGNATURE: unable to decrypt certificate's signature\fR" 4
371 .IX Item "4 X509_V_ERR_UNABLE_TO_DECRYPT_CERT_SIGNATURE: unable to decrypt certificate's signature"
372 the certificate signature could not be decrypted. This means that the actual signature value
373 could not be determined rather than it not matching the expected value, this is only
374 meaningful for \s-1RSA\s0 keys.
375 .IP "\fB5 X509_V_ERR_UNABLE_TO_DECRYPT_CRL_SIGNATURE: unable to decrypt \s-1CRL\s0's signature\fR" 4
376 .IX Item "5 X509_V_ERR_UNABLE_TO_DECRYPT_CRL_SIGNATURE: unable to decrypt CRL's signature"
377 the \s-1CRL\s0 signature could not be decrypted: this means that the actual signature value
378 could not be determined rather than it not matching the expected value. Unused.
379 .IP "\fB6 X509_V_ERR_UNABLE_TO_DECODE_ISSUER_PUBLIC_KEY: unable to decode issuer public key\fR" 4
380 .IX Item "6 X509_V_ERR_UNABLE_TO_DECODE_ISSUER_PUBLIC_KEY: unable to decode issuer public key"
381 the public key in the certificate SubjectPublicKeyInfo could not be read.
382 .IP "\fB7 X509_V_ERR_CERT_SIGNATURE_FAILURE: certificate signature failure\fR" 4
383 .IX Item "7 X509_V_ERR_CERT_SIGNATURE_FAILURE: certificate signature failure"
384 the signature of the certificate is invalid.
385 .IP "\fB8 X509_V_ERR_CRL_SIGNATURE_FAILURE: \s-1CRL\s0 signature failure\fR" 4
386 .IX Item "8 X509_V_ERR_CRL_SIGNATURE_FAILURE: CRL signature failure"
387 the signature of the certificate is invalid.
388 .IP "\fB9 X509_V_ERR_CERT_NOT_YET_VALID: certificate is not yet valid\fR" 4
389 .IX Item "9 X509_V_ERR_CERT_NOT_YET_VALID: certificate is not yet valid"
390 the certificate is not yet valid: the notBefore date is after the current time.
391 .IP "\fB10 X509_V_ERR_CERT_HAS_EXPIRED: certificate has expired\fR" 4
392 .IX Item "10 X509_V_ERR_CERT_HAS_EXPIRED: certificate has expired"
393 the certificate has expired: that is the notAfter date is before the current time.
394 .IP "\fB11 X509_V_ERR_CRL_NOT_YET_VALID: \s-1CRL\s0 is not yet valid\fR" 4
395 .IX Item "11 X509_V_ERR_CRL_NOT_YET_VALID: CRL is not yet valid"
396 the \s-1CRL\s0 is not yet valid.
397 .IP "\fB12 X509_V_ERR_CRL_HAS_EXPIRED: \s-1CRL\s0 has expired\fR" 4
398 .IX Item "12 X509_V_ERR_CRL_HAS_EXPIRED: CRL has expired"
399 the \s-1CRL\s0 has expired.
400 .IP "\fB13 X509_V_ERR_ERROR_IN_CERT_NOT_BEFORE_FIELD: format error in certificate's notBefore field\fR" 4
401 .IX Item "13 X509_V_ERR_ERROR_IN_CERT_NOT_BEFORE_FIELD: format error in certificate's notBefore field"
402 the certificate notBefore field contains an invalid time.
403 .IP "\fB14 X509_V_ERR_ERROR_IN_CERT_NOT_AFTER_FIELD: format error in certificate's notAfter field\fR" 4
404 .IX Item "14 X509_V_ERR_ERROR_IN_CERT_NOT_AFTER_FIELD: format error in certificate's notAfter field"
405 the certificate notAfter field contains an invalid time.
406 .IP "\fB15 X509_V_ERR_ERROR_IN_CRL_LAST_UPDATE_FIELD: format error in \s-1CRL\s0's lastUpdate field\fR" 4
407 .IX Item "15 X509_V_ERR_ERROR_IN_CRL_LAST_UPDATE_FIELD: format error in CRL's lastUpdate field"
408 the \s-1CRL\s0 lastUpdate field contains an invalid time.
409 .IP "\fB16 X509_V_ERR_ERROR_IN_CRL_NEXT_UPDATE_FIELD: format error in \s-1CRL\s0's nextUpdate field\fR" 4
410 .IX Item "16 X509_V_ERR_ERROR_IN_CRL_NEXT_UPDATE_FIELD: format error in CRL's nextUpdate field"
411 the \s-1CRL\s0 nextUpdate field contains an invalid time.
412 .IP "\fB17 X509_V_ERR_OUT_OF_MEM: out of memory\fR" 4
413 .IX Item "17 X509_V_ERR_OUT_OF_MEM: out of memory"
414 an error occurred trying to allocate memory. This should never happen.
415 .IP "\fB18 X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT: self signed certificate\fR" 4
416 .IX Item "18 X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT: self signed certificate"
417 the passed certificate is self signed and the same certificate cannot be found in the list of
418 trusted certificates.
419 .IP "\fB19 X509_V_ERR_SELF_SIGNED_CERT_IN_CHAIN: self signed certificate in certificate chain\fR" 4
420 .IX Item "19 X509_V_ERR_SELF_SIGNED_CERT_IN_CHAIN: self signed certificate in certificate chain"
421 the certificate chain could be built up using the untrusted certificates but the root could not
423 .IP "\fB20 X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT_LOCALLY: unable to get local issuer certificate\fR" 4
424 .IX Item "20 X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT_LOCALLY: unable to get local issuer certificate"
425 the issuer certificate could not be found: this occurs if the issuer
426 certificate of an untrusted certificate cannot be found.
427 .IP "\fB21 X509_V_ERR_UNABLE_TO_VERIFY_LEAF_SIGNATURE: unable to verify the first certificate\fR" 4
428 .IX Item "21 X509_V_ERR_UNABLE_TO_VERIFY_LEAF_SIGNATURE: unable to verify the first certificate"
429 no signatures could be verified because the chain contains only one certificate and it is not
431 .IP "\fB22 X509_V_ERR_CERT_CHAIN_TOO_LONG: certificate chain too long\fR" 4
432 .IX Item "22 X509_V_ERR_CERT_CHAIN_TOO_LONG: certificate chain too long"
433 the certificate chain length is greater than the supplied maximum depth. Unused.
434 .IP "\fB23 X509_V_ERR_CERT_REVOKED: certificate revoked\fR" 4
435 .IX Item "23 X509_V_ERR_CERT_REVOKED: certificate revoked"
436 the certificate has been revoked.
437 .IP "\fB24 X509_V_ERR_INVALID_CA: invalid \s-1CA\s0 certificate\fR" 4
438 .IX Item "24 X509_V_ERR_INVALID_CA: invalid CA certificate"
439 a \s-1CA\s0 certificate is invalid. Either it is not a \s-1CA\s0 or its extensions are not consistent
440 with the supplied purpose.
441 .IP "\fB25 X509_V_ERR_PATH_LENGTH_EXCEEDED: path length constraint exceeded\fR" 4
442 .IX Item "25 X509_V_ERR_PATH_LENGTH_EXCEEDED: path length constraint exceeded"
443 the basicConstraints pathlength parameter has been exceeded.
444 .IP "\fB26 X509_V_ERR_INVALID_PURPOSE: unsupported certificate purpose\fR" 4
445 .IX Item "26 X509_V_ERR_INVALID_PURPOSE: unsupported certificate purpose"
446 the supplied certificate cannot be used for the specified purpose.
447 .IP "\fB27 X509_V_ERR_CERT_UNTRUSTED: certificate not trusted\fR" 4
448 .IX Item "27 X509_V_ERR_CERT_UNTRUSTED: certificate not trusted"
449 the root \s-1CA\s0 is not marked as trusted for the specified purpose.
450 .IP "\fB28 X509_V_ERR_CERT_REJECTED: certificate rejected\fR" 4
451 .IX Item "28 X509_V_ERR_CERT_REJECTED: certificate rejected"
452 the root \s-1CA\s0 is marked to reject the specified purpose.
453 .IP "\fB29 X509_V_ERR_SUBJECT_ISSUER_MISMATCH: subject issuer mismatch\fR" 4
454 .IX Item "29 X509_V_ERR_SUBJECT_ISSUER_MISMATCH: subject issuer mismatch"
455 the current candidate issuer certificate was rejected because its subject name
456 did not match the issuer name of the current certificate. Only displayed when
457 the \fB\-issuer_checks\fR option is set.
458 .IP "\fB30 X509_V_ERR_AKID_SKID_MISMATCH: authority and subject key identifier mismatch\fR" 4
459 .IX Item "30 X509_V_ERR_AKID_SKID_MISMATCH: authority and subject key identifier mismatch"
460 the current candidate issuer certificate was rejected because its subject key
461 identifier was present and did not match the authority key identifier current
462 certificate. Only displayed when the \fB\-issuer_checks\fR option is set.
463 .IP "\fB31 X509_V_ERR_AKID_ISSUER_SERIAL_MISMATCH: authority and issuer serial number mismatch\fR" 4
464 .IX Item "31 X509_V_ERR_AKID_ISSUER_SERIAL_MISMATCH: authority and issuer serial number mismatch"
465 the current candidate issuer certificate was rejected because its issuer name
466 and serial number was present and did not match the authority key identifier
467 of the current certificate. Only displayed when the \fB\-issuer_checks\fR option is set.
468 .IP "\fB32 X509_V_ERR_KEYUSAGE_NO_CERTSIGN:key usage does not include certificate signing\fR" 4
469 .IX Item "32 X509_V_ERR_KEYUSAGE_NO_CERTSIGN:key usage does not include certificate signing"
470 the current candidate issuer certificate was rejected because its keyUsage extension
471 does not permit certificate signing.
472 .IP "\fB50 X509_V_ERR_APPLICATION_VERIFICATION: application verification failure\fR" 4
473 .IX Item "50 X509_V_ERR_APPLICATION_VERIFICATION: application verification failure"
474 an application specific error. Unused.
477 Although the issuer checks are a considerable improvement over the old technique they still
478 suffer from limitations in the underlying X509_LOOKUP \s-1API.\s0 One consequence of this is that
479 trusted certificates with matching subject name must either appear in a file (as specified by the
480 \&\fB\-CAfile\fR option) or a directory (as specified by \fB\-CApath\fR. If they occur in both then only
481 the certificates in the file will be recognised.
483 Previous versions of OpenSSL assume certificates with matching subject name are identical and
486 Previous versions of this documentation swapped the meaning of the
487 \&\fBX509_V_ERR_UNABLE_TO_GET_ISSUER_CERT\fR and
488 \&\fB20 X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT_LOCALLY\fR error codes.
490 .IX Header "SEE ALSO"
494 The \-no_alt_chains options was first added to OpenSSL 1.0.1n and 1.0.2b.
projects / FreeBSD / stable / 10.git / blob