verify.pod 22.1 KB
Newer Older
1 2 3 4
=pod

=head1 NAME

5
verify - Utility to verify certificates.
6 7 8 9

=head1 SYNOPSIS

B<openssl> B<verify>
10
[B<-help>]
11
[B<-CAfile file>]
12
[B<-CApath directory>]
13 14
[B<-no-CAfile>]
[B<-no-CApath>]
15
[B<-attime timestamp>]
16
[B<-check_ss_sig>]
R
Rich Salz 已提交
17
[B<-CRLfile file>]
18
[B<-crl_download>]
D
Dr. Stephen Henson 已提交
19 20
[B<-crl_check>]
[B<-crl_check_all>]
21
[B<-engine id>]
D
Dr. Stephen Henson 已提交
22 23
[B<-explicit_policy>]
[B<-extended_crl>]
24 25 26
[B<-ignore_critical>]
[B<-inhibit_any>]
[B<-inhibit_map>]
27
[B<-partial_chain>]
28 29 30 31
[B<-policy arg>]
[B<-policy_check>]
[B<-policy_print>]
[B<-purpose purpose>]
32 33 34
[B<-suiteB_128>]
[B<-suiteB_128_only>]
[B<-suiteB_192>]
35
[B<-trusted_first>]
36
[B<-no_alt_chains>]
37
[B<-untrusted file>]
38
[B<-trusted file>]
39
[B<-use_deltas>]
40
[B<-verbose>]
41
[B<-auth_level level>]
42 43 44 45 46
[B<-verify_depth num>]
[B<-verify_email email>]
[B<-verify_hostname hostname>]
[B<-verify_ip ip>]
[B<-verify_name name>]
47
[B<-x509_strict>]
48
[B<-show_chain>]
49 50 51 52 53 54 55 56 57 58 59
[B<->]
[certificates]

=head1 DESCRIPTION

The B<verify> command verifies certificate chains.

=head1 COMMAND OPTIONS

=over 4

60 61 62 63
=item B<-help>

Print out a usage message.

64 65
=item B<-CAfile file>

66 67
A B<file> of trusted certificates.
The file should contain one or more certificates in PEM format.
68

69 70 71 72 73 74 75 76
=item B<-CApath directory>

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 hashed certificate subject name: see the B<-hash> option
of the B<x509> utility). Under Unix the B<c_rehash> script will automatically
create symbolic links to a directory of certificates.

77 78 79 80 81 82 83 84
=item B<-no-CAfile>

Do not load the trusted CA certificates from the default file location

=item B<-no-CApath>

Do not load the trusted CA certificates from the default directory location

85
=item B<-attime timestamp>
86

87 88 89
Perform validation checks using time specified by B<timestamp> and not
current system time. B<timestamp> is the number of seconds since
01.01.1970 (UNIX time).
90

91
=item B<-check_ss_sig>
92

93 94
Verify the signature on the self-signed root CA. This is disabled by default
because it doesn't add any security.
95

R
Rich Salz 已提交
96
=item B<-CRLfile file>
97

98 99 100
The B<file> should contain one or more CRLs in PEM format.
This option can be specified more than once to include CRLs from multiple
B<files>.
101

102 103 104 105
=item B<-crl_download>

Attempt to download CRL information for this certificate.

106
=item B<-crl_check>
107

108 109
Checks end entity certificate validity by attempting to look up a valid CRL.
If a valid CRL cannot be found an error occurs.
110

111
=item B<-crl_check_all>
112

113 114 115
Checks the validity of B<all> certificates in the chain by attempting
to look up valid CRLs.

116 117 118 119 120 121 122 123 124
=item B<-engine id>

Specifying an engine B<id> will cause L<verify(1)> to attempt to load the
specified engine.
The engine will then be set as the default for all its supported algorithms.
If you want to load certificates or CRLs that require engine support via any of
the B<-trusted>, B<-untrusted> or B<-CRLfile> options, the B<-engine> option
must be specified before those options.

125 126 127 128 129 130 131 132
=item B<-explicit_policy>

Set policy variable require-explicit-policy (see RFC5280).

=item B<-extended_crl>

Enable extended CRL features such as indirect CRLs and alternate CRL
signing keys.
133

134
=item B<-ignore_critical>
135

136 137 138 139 140 141 142 143 144 145 146
Normally if an unhandled critical extension is present which is not
supported by OpenSSL the certificate is rejected (as required by RFC5280).
If this option is set critical extensions are ignored.

=item B<-inhibit_any>

Set policy variable inhibit-any-policy (see RFC5280).

=item B<-inhibit_map>

Set policy variable inhibit-policy-mapping (see RFC5280).
147

148
=item B<-partial_chain>
149

150 151 152
Allow verification to succeed even if a I<complete> chain cannot be built to a
self-signed trust-anchor, provided it is possible to construct a chain to a
trusted certificate that might not be self-signed.
153

D
Dr. Stephen Henson 已提交
154 155
=item B<-policy arg>

156 157 158
Enable policy processing and add B<arg> to the user-initial-policy-set (see
RFC5280). The policy B<arg> can be an object name an OID in numeric form.
This argument can appear more than once.
D
Dr. Stephen Henson 已提交
159 160 161 162 163 164 165

=item B<-policy_check>

Enables certificate policy processing.

=item B<-policy_print>

166
Print out diagnostics related to policy processing.
D
Dr. Stephen Henson 已提交
167

168
=item B<-purpose purpose>
D
Dr. Stephen Henson 已提交
169

170 171 172 173 174
The intended use for the certificate. If this option is not specified,
B<verify> will not consider certificate purpose during chain verification.
Currently accepted uses are B<sslclient>, B<sslserver>, B<nssslserver>,
B<smimesign>, B<smimeencrypt>. See the B<VERIFY OPERATION> section for more
information.
D
Dr. Stephen Henson 已提交
175

176
=item B<-suiteB_128_only>, B<-suiteB_128>, B<-suiteB_192>
D
Dr. Stephen Henson 已提交
177

178 179 180 181 182
enable the Suite B mode operation at 128 bit Level of Security, 128 bit or
192 bit, or only 192 bit Level of Security respectively.
See RFC6460 for details. In particular the supported signature algorithms are
reduced to support only ECDSA and SHA256 or SHA384 and only the elliptic curves
P-256 and P-384.
D
Dr. Stephen Henson 已提交
183

184
=item B<-trusted_first>
D
Dr. Stephen Henson 已提交
185

186 187 188 189
When constructing the certificate chain, use the trusted certificates specified
via B<-CAfile>, B<-CApath> or B<-trusted> before any certificates specified via
B<-untrusted>.
This can be useful in environments with Bridge or Cross-Certified CAs.
190
As of OpenSSL 1.1.0 this option is on by default and cannot be disabled.
D
Dr. Stephen Henson 已提交
191

192 193
=item B<-no_alt_chains>

194 195 196 197 198 199
By default, unless B<-trusted_first> is specified, when building a certificate
chain, if the first certificate chain found is not trusted, then OpenSSL will
attempt to replace untrusted issuer certificates with certificates from the
trust store to see if an alternative chain can be found that is trusted.
As of OpenSSL 1.1.0, with B<-trusted_first> always on, this option has no
effect.
200

201
=item B<-untrusted file>
D
Dr. Stephen Henson 已提交
202

203
A B<file> of additional untrusted certificates (intermediate issuer CAs) used
A
Alex Gaynor 已提交
204
to construct a certificate chain from the subject certificate to a trust-anchor.
205 206 207
The B<file> should contain one or more certificates in PEM format.
This option can be specified more than once to include untrusted certiificates
from multiple B<files>.
D
Dr. Stephen Henson 已提交
208

209 210
=item B<-trusted file>

211 212 213 214 215 216 217 218 219 220 221
A B<file> of trusted certificates, which must be self-signed, unless the
B<-partial_chain> option is specified.
The B<file> contain one or more certificates in PEM format.
With this option, no additional (e.g., default) certificate lists are
consulted.
That is, the only trust-anchors are those listed in B<file>.
This option can be specified more than once to include trusted certificates
from multiple B<files>.
This option implies the B<-no-CAfile> and B<-no-CApath> options.
This option cannot be used in combination with either of the B<-CAfile> or
B<-CApath> options.
222

D
Dr. Stephen Henson 已提交
223 224 225 226
=item B<-use_deltas>

Enable support for delta CRLs.

227
=item B<-verbose>
228

229
Print extra information about the operations being performed.
230

231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248
=item B<-auth_level level>

Set the certificate chain authentication security level to B<level>.
The authentication security level determines the acceptable signature and
public key strength when verifying certificate chains.
For a certificate chain to validate, the public keys of all the certificates
must meet the specified security B<level>.
The signature algorithm security level is enforced for all the certificates in
the chain except for the chain's I<trust anchor>, which is either directly
trusted or validated by means other than its signature.
See L<SSL_CTX_set_security_level(3)> for the definitions of the available
levels.
The default security level is -1, or "not set".
At security level 0 or lower all algorithms are acceptable.
Security level 1 requires at least 80-bit-equivalent security and is broadly
interoperable, though it will, for example, reject MD5 signatures or RSA keys
shorter than 1024 bits.

249 250
=item B<-verify_depth num>

251 252 253 254
Limit the certificate chain to B<num> intermediate CA certificates.
A maximal depth chain can have up to B<num+2> certificates, since neither the
end-entity certificate nor the trust-anchor certificate count against the
B<-verify_depth> limit.
255 256 257 258

=item B<-verify_email email>

Verify if the B<email> matches the email address in Subject Alternative Name or
M
Matt Caswell 已提交
259
the email in the subject Distinguished Name.
260 261 262 263 264 265 266 267 268 269 270 271 272

=item B<-verify_hostname hostname>

Verify if the B<hostname> matches DNS name in Subject Alternative Name or
Common Name in the subject certificate.

=item B<-verify_ip ip>

Verify if the B<ip> matches the IP address in Subject Alternative Name of
the subject certificate.

=item B<-verify_name name>

273
Use default verification policies like trust model and required certificate
274
policies identified by B<name>.
275 276 277 278
The trust model determines which auxiliary trust or reject OIDs are applicable
to verifying the given certificate chain.
See the B<-addtrust> and B<-addreject> options of the L<x509(1)> command-line
utility.
279 280
Supported policy names include: B<default>, B<pkcs7>, B<smime_sign>,
B<ssl_client>, B<ssl_server>.
281 282 283 284 285
These mimics the combinations of purpose and trust settings used in SSL, CMS
and S/MIME.
As of OpenSSL 1.1.0, the trust model is inferred from the purpose when not
specified, so the B<-verify_name> options are functionally equivalent to the
corresponding B<-purpose> settings.
286

287 288 289 290 291
=item B<-x509_strict>

For strict X.509 compliance, disable non-compliant workarounds for broken
certificates.

292 293 294 295 296 297
=item B<-show_chain>

Display information about the certificate chain that has been built (if
successful). Certificates in the chain that came from the untrusted list will be
flagged as "untrusted".

298 299
=item B<->

300
Indicates the last option. All arguments following this are assumed to be
301 302
certificate files. This is useful if the first certificate filename begins
with a B<->.
303 304 305

=item B<certificates>

306 307 308
One or more certificates to verify. If no certificates are given, B<verify>
will attempt to read a certificate from standard input. Certificates must be
in PEM format.
309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326

=back

=head1 VERIFY OPERATION

The B<verify> program 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 B<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
327 328 329 330 331 332 333 334 335 336 337 338 339 340 341
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.
Ater 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.
D
Dr. Stephen Henson 已提交
342

343
The lookup first looks in the list of untrusted certificates and if no match
344
is found the remaining lookups are from the trusted certificates. The root CA
345 346 347 348 349 350 351 352 353
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 B<-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
354
the B<CERTIFICATE EXTENSIONS> section of the B<x509> utility.
355

356 357 358 359
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 OpenSSL, a certificate with no
trust settings is considered to be valid for all purposes.
360 361 362 363 364 365 366 367 368

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.

369 370 371 372 373 374 375 376 377 378 379 380 381 382 383
=head1 DIAGNOSTICS

When 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.

384
An partial list of the error codes and messages is shown below, this also
385 386 387 388 389 390 391 392 393 394
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".

=over 4

=item B<0 X509_V_OK: ok>

the operation was successful.

395 396 397 398
=item B<1 X509_V_ERR_UNSPECIFIED: unspecified certificate verification error>

unspecified error, should not happen.

399 400
=item B<2 X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT: unable to get issuer certificate>

401 402
the issuer certificate of a looked up certificate could not be found. This
normally means the list of trusted certificates is not complete.
403

L
Lutz Jänicke 已提交
404
=item B<3 X509_V_ERR_UNABLE_TO_GET_CRL: unable to get certificate CRL>
405

D
Dr. Stephen Henson 已提交
406
the CRL of a certificate could not be found.
407 408 409 410 411 412 413

=item B<4 X509_V_ERR_UNABLE_TO_DECRYPT_CERT_SIGNATURE: unable to decrypt certificate's signature>

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.

414
=item B<5 X509_V_ERR_UNABLE_TO_DECRYPT_CRL_SIGNATURE: unable to decrypt CRL's signature>
415 416 417 418 419 420 421 422 423 424 425 426 427 428

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.

=item B<6 X509_V_ERR_UNABLE_TO_DECODE_ISSUER_PUBLIC_KEY: unable to decode issuer public key>

the public key in the certificate SubjectPublicKeyInfo could not be read.

=item B<7 X509_V_ERR_CERT_SIGNATURE_FAILURE: certificate signature failure>

the signature of the certificate is invalid.

=item B<8 X509_V_ERR_CRL_SIGNATURE_FAILURE: CRL signature failure>

D
Dr. Stephen Henson 已提交
429
the signature of the certificate is invalid.
430 431 432 433 434

=item B<9 X509_V_ERR_CERT_NOT_YET_VALID: certificate is not yet valid>

the certificate is not yet valid: the notBefore date is after the current time.

435
=item B<10 X509_V_ERR_CERT_HAS_EXPIRED: certificate has expired>
436

437
the certificate has expired: that is the notAfter date is before the current time.
438

439
=item B<11 X509_V_ERR_CRL_NOT_YET_VALID: CRL is not yet valid>
440

D
Dr. Stephen Henson 已提交
441
the CRL is not yet valid.
442 443 444

=item B<12 X509_V_ERR_CRL_HAS_EXPIRED: CRL has expired>

D
Dr. Stephen Henson 已提交
445
the CRL has expired.
446 447 448 449

=item B<13 X509_V_ERR_ERROR_IN_CERT_NOT_BEFORE_FIELD: format error in certificate's notBefore field>

the certificate notBefore field contains an invalid time.
450

451 452 453 454 455 456
=item B<14 X509_V_ERR_ERROR_IN_CERT_NOT_AFTER_FIELD: format error in certificate's notAfter field>

the certificate notAfter field contains an invalid time.

=item B<15 X509_V_ERR_ERROR_IN_CRL_LAST_UPDATE_FIELD: format error in CRL's lastUpdate field>

D
Dr. Stephen Henson 已提交
457
the CRL lastUpdate field contains an invalid time.
458 459 460

=item B<16 X509_V_ERR_ERROR_IN_CRL_NEXT_UPDATE_FIELD: format error in CRL's nextUpdate field>

D
Dr. Stephen Henson 已提交
461
the CRL nextUpdate field contains an invalid time.
462 463 464

=item B<17 X509_V_ERR_OUT_OF_MEM: out of memory>

465
an error occurred trying to allocate memory. This should never happen.
466 467 468 469 470 471 472 473 474 475 476 477 478

=item B<18 X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT: self signed certificate>

the passed certificate is self signed and the same certificate cannot be found in the list of
trusted certificates.

=item B<19 X509_V_ERR_SELF_SIGNED_CERT_IN_CHAIN: self signed certificate in certificate chain>

the certificate chain could be built up using the untrusted certificates but the root could not
be found locally.

=item B<20 X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT_LOCALLY: unable to get local issuer certificate>

479 480
the issuer certificate could not be found: this occurs if the issuer
certificate of an untrusted certificate cannot be found.
481 482 483 484 485 486 487 488 489 490 491 492

=item B<21 X509_V_ERR_UNABLE_TO_VERIFY_LEAF_SIGNATURE: unable to verify the first certificate>

no signatures could be verified because the chain contains only one certificate and it is not
self signed.

=item B<22 X509_V_ERR_CERT_CHAIN_TOO_LONG: certificate chain too long>

the certificate chain length is greater than the supplied maximum depth. Unused.

=item B<23 X509_V_ERR_CERT_REVOKED: certificate revoked>

D
Dr. Stephen Henson 已提交
493
the certificate has been revoked.
494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515

=item B<24 X509_V_ERR_INVALID_CA: invalid CA certificate>

a CA certificate is invalid. Either it is not a CA or its extensions are not consistent
with the supplied purpose.

=item B<25 X509_V_ERR_PATH_LENGTH_EXCEEDED: path length constraint exceeded>

the basicConstraints pathlength parameter has been exceeded.

=item B<26 X509_V_ERR_INVALID_PURPOSE: unsupported certificate purpose>

the supplied certificate cannot be used for the specified purpose.

=item B<27 X509_V_ERR_CERT_UNTRUSTED: certificate not trusted>

the root CA is not marked as trusted for the specified purpose.

=item B<28 X509_V_ERR_CERT_REJECTED: certificate rejected>

the root CA is marked to reject the specified purpose.

D
Dr. Stephen Henson 已提交
516 517
=item B<29 X509_V_ERR_SUBJECT_ISSUER_MISMATCH: subject issuer mismatch>

518 519
Not used as of OpenSSL 1.1.0 as a result of the deprecation of the
B<-issuer_checks> option.
D
Dr. Stephen Henson 已提交
520 521 522

=item B<30 X509_V_ERR_AKID_SKID_MISMATCH: authority and subject key identifier mismatch>

523 524
Not used as of OpenSSL 1.1.0 as a result of the deprecation of the
B<-issuer_checks> option.
D
Dr. Stephen Henson 已提交
525 526 527

=item B<31 X509_V_ERR_AKID_ISSUER_SERIAL_MISMATCH: authority and issuer serial number mismatch>

528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592
Not used as of OpenSSL 1.1.0 as a result of the deprecation of the
B<-issuer_checks> option.

=item B<32 X509_V_ERR_KEYUSAGE_NO_CERTSIGN: key usage does not include certificate signing>

Not used as of OpenSSL 1.1.0 as a result of the deprecation of the
B<-issuer_checks> option.

=item B<33 X509_V_ERR_UNABLE_TO_GET_CRL_ISSUER: unable to get CRL issuer certificate>

TBA

=item B<34 X509_V_ERR_UNHANDLED_CRITICAL_EXTENSION: unhandled critical extension>

TBA

=item B<35 X509_V_ERR_KEYUSAGE_NO_CRL_SIGN: key usage does not include CRL signing>

TBA

=item B<36 X509_V_ERR_UNHANDLED_CRITICAL_CRL_EXTENSION: unhandled critical CRL extension>

TBA

=item B<37 X509_V_ERR_INVALID_NON_CA: invalid non-CA certificate has CA markings>

TBA

=item B<38 X509_V_ERR_PROXY_PATH_LENGTH_EXCEEDED: proxy path length constraint exceeded>

TBA

=item B<39 X509_V_ERR_KEYUSAGE_NO_DIGITAL_SIGNATURE: key usage does not include digital signature>

TBA

=item B<40 X509_V_ERR_PROXY_CERTIFICATES_NOT_ALLOWED: proxy certificates not allowed, please set the appropriate flag>

TBA

=item B<41 X509_V_ERR_INVALID_EXTENSION: invalid or inconsistent certificate extension>

TBA

=item B<42 X509_V_ERR_INVALID_POLICY_EXTENSION: invalid or inconsistent certificate policy extension>

TBA

=item B<43 X509_V_ERR_NO_EXPLICIT_POLICY: no explicit policy>

TBA

=item B<44 X509_V_ERR_DIFFERENT_CRL_SCOPE: Different CRL scope>

TBA

=item B<45 X509_V_ERR_UNSUPPORTED_EXTENSION_FEATURE: Unsupported extension feature>

TBA

=item B<46 X509_V_ERR_UNNESTED_RESOURCE: RFC 3779 resource not subset of parent's resources>

TBA

=item B<47 X509_V_ERR_PERMITTED_VIOLATION: permitted subtree violation>
D
Dr. Stephen Henson 已提交
593

594
TBA
D
Dr. Stephen Henson 已提交
595

596 597 598 599 600 601 602
=item B<48 X509_V_ERR_EXCLUDED_VIOLATION: excluded subtree violation>

TBA

=item B<49 X509_V_ERR_SUBTREE_MINMAX: name constraints minimum and maximum not supported>

TBA
D
Dr. Stephen Henson 已提交
603

604 605 606 607
=item B<50 X509_V_ERR_APPLICATION_VERIFICATION: application verification failure>

an application specific error. Unused.

608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669
=item B<51 X509_V_ERR_UNSUPPORTED_CONSTRAINT_TYPE: unsupported name constraint type>

TBA

=item B<52 X509_V_ERR_UNSUPPORTED_CONSTRAINT_SYNTAX: unsupported or invalid name constraint syntax>

TBA

=item B<53 X509_V_ERR_UNSUPPORTED_NAME_SYNTAX: unsupported or invalid name syntax>

TBA

=item B<54 X509_V_ERR_CRL_PATH_VALIDATION_ERROR: CRL path validation error>

TBA

=item B<55 X509_V_ERR_PATH_LOOP: Path Loop>

TBA

=item B<56 X509_V_ERR_SUITE_B_INVALID_VERSION: Suite B: certificate version invalid>

TBA

=item B<57 X509_V_ERR_SUITE_B_INVALID_ALGORITHM: Suite B: invalid public key algorithm>

TBA

=item B<58 X509_V_ERR_SUITE_B_INVALID_CURVE: Suite B: invalid ECC curve>

TBA

=item B<59 X509_V_ERR_SUITE_B_INVALID_SIGNATURE_ALGORITHM: Suite B: invalid signature algorithm>

TBA

=item B<60 X509_V_ERR_SUITE_B_LOS_NOT_ALLOWED: Suite B: curve not allowed for this LOS>

TBA

=item B<61 X509_V_ERR_SUITE_B_CANNOT_SIGN_P_384_WITH_P_256: Suite B: cannot sign P-384 with P-256>

TBA

=item B<62 X509_V_ERR_HOSTNAME_MISMATCH: Hostname mismatch>

TBA

=item B<63 X509_V_ERR_EMAIL_MISMATCH: Email address mismatch>

TBA

=item B<64 X509_V_ERR_IP_ADDRESS_MISMATCH: IP address mismatch>

TBA

=item B<65 X509_V_ERR_DANE_NO_MATCH: No matching DANE TLSA records>

DANE TLSA authentication is enabled, but no TLSA records matched the
certificate chain.
This error is only possible in L<s_client(1)>.

670
=back
671

D
Dr. Stephen Henson 已提交
672 673
=head1 BUGS

674
Although the issuer checks are a considerable improvement over the old technique they still
D
Dr. Stephen Henson 已提交
675 676
suffer from limitations in the underlying X509_LOOKUP API. One consequence of this is that
trusted certificates with matching subject name must either appear in a file (as specified by the
M
Matt Caswell 已提交
677
B<-CAfile> option) or a directory (as specified by B<-CApath>). If they occur in both then only
D
Dr. Stephen Henson 已提交
678 679 680 681 682
the certificates in the file will be recognised.

Previous versions of OpenSSL assume certificates with matching subject name are identical and
mishandled them.

683 684 685 686
Previous versions of this documentation swapped the meaning of the
B<X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT> and
B<20 X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT_LOCALLY> error codes.

687 688
=head1 SEE ALSO

R
Rich Salz 已提交
689
L<x509(1)>
690

691 692
=head1 HISTORY

693 694 695 696
The B<-show_chain> option was first added to OpenSSL 1.1.0.

The B<-issuer_checks> option is deprecated as of OpenSSL 1.1.0 and
is silently ignored.
697

698
=cut
699