| 1 | .\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14 |
| 2 | .\" |
| 3 | .\" Standard preamble: |
| 4 | .\" ======================================================================== |
| 5 | .de Sh \" Subsection heading |
| 6 | .br |
| 7 | .if t .Sp |
| 8 | .ne 5 |
| 9 | .PP |
| 10 | \fB\\$1\fR |
| 11 | .PP |
| 12 | .. |
| 13 | .de Sp \" Vertical space (when we can't use .PP) |
| 14 | .if t .sp .5v |
| 15 | .if n .sp |
| 16 | .. |
| 17 | .de Vb \" Begin verbatim text |
| 18 | .ft CW |
| 19 | .nf |
| 20 | .ne \\$1 |
| 21 | .. |
| 22 | .de Ve \" End verbatim text |
| 23 | .ft R |
| 24 | .fi |
| 25 | .. |
| 26 | .\" Set up some character translations and predefined strings. \*(-- will |
| 27 | .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left |
| 28 | .\" double quote, and \*(R" will give a right double quote. | will give a |
| 29 | .\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to |
| 30 | .\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C' |
| 31 | .\" expand to `' in nroff, nothing in troff, for use with C<>. |
| 32 | .tr \(*W-|\(bv\*(Tr |
| 33 | .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' |
| 34 | .ie n \{\ |
| 35 | . ds -- \(*W- |
| 36 | . ds PI pi |
| 37 | . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch |
| 38 | . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch |
| 39 | . ds L" "" |
| 40 | . ds R" "" |
| 41 | . ds C` "" |
| 42 | . ds C' "" |
| 43 | 'br\} |
| 44 | .el\{\ |
| 45 | . ds -- \|\(em\| |
| 46 | . ds PI \(*p |
| 47 | . ds L" `` |
| 48 | . ds R" '' |
| 49 | 'br\} |
| 50 | .\" |
| 51 | .\" If the F register is turned on, we'll generate index entries on stderr for |
| 52 | .\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index |
| 53 | .\" entries marked with X<> in POD. Of course, you'll have to process the |
| 54 | .\" output yourself in some meaningful fashion. |
| 55 | .if \nF \{\ |
| 56 | . de IX |
| 57 | . tm Index:\\$1\t\\n%\t"\\$2" |
| 58 | .. |
| 59 | . nr % 0 |
| 60 | . rr F |
| 61 | .\} |
| 62 | .\" |
| 63 | .\" For nroff, turn off justification. Always turn off hyphenation; it makes |
| 64 | .\" way too many mistakes in technical documents. |
| 65 | .hy 0 |
| 66 | .if n .na |
| 67 | .\" |
| 68 | .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). |
| 69 | .\" Fear. Run. Save yourself. No user-serviceable parts. |
| 70 | . \" fudge factors for nroff and troff |
| 71 | .if n \{\ |
| 72 | . ds #H 0 |
| 73 | . ds #V .8m |
| 74 | . ds #F .3m |
| 75 | . ds #[ \f1 |
| 76 | . ds #] \fP |
| 77 | .\} |
| 78 | .if t \{\ |
| 79 | . ds #H ((1u-(\\\\n(.fu%2u))*.13m) |
| 80 | . ds #V .6m |
| 81 | . ds #F 0 |
| 82 | . ds #[ \& |
| 83 | . ds #] \& |
| 84 | .\} |
| 85 | . \" simple accents for nroff and troff |
| 86 | .if n \{\ |
| 87 | . ds ' \& |
| 88 | . ds ` \& |
| 89 | . ds ^ \& |
| 90 | . ds , \& |
| 91 | . ds ~ ~ |
| 92 | . ds / |
| 93 | .\} |
| 94 | .if t \{\ |
| 95 | . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" |
| 96 | . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' |
| 97 | . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' |
| 98 | . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' |
| 99 | . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' |
| 100 | . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' |
| 101 | .\} |
| 102 | . \" troff and (daisy-wheel) nroff accents |
| 103 | .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V' |
| 104 | .ds 8 \h'\*(#H'\(*b\h'-\*(#H' |
| 105 | .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#] |
| 106 | .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H' |
| 107 | .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u' |
| 108 | .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#] |
| 109 | .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#] |
| 110 | .ds ae a\h'-(\w'a'u*4/10)'e |
| 111 | .ds Ae A\h'-(\w'A'u*4/10)'E |
| 112 | . \" corrections for vroff |
| 113 | .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u' |
| 114 | .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u' |
| 115 | . \" for low resolution devices (crt and lpr) |
| 116 | .if \n(.H>23 .if \n(.V>19 \ |
| 117 | \{\ |
| 118 | . ds : e |
| 119 | . ds 8 ss |
| 120 | . ds o a |
| 121 | . ds d- d\h'-1'\(ga |
| 122 | . ds D- D\h'-1'\(hy |
| 123 | . ds th \o'bp' |
| 124 | . ds Th \o'LP' |
| 125 | . ds ae ae |
| 126 | . ds Ae AE |
| 127 | .\} |
| 128 | .rm #[ #] #H #V #F C |
| 129 | .\" ======================================================================== |
| 130 | .\" |
| 131 | .IX Title "VERIFY 1" |
| 132 | .TH VERIFY 1 "2004-12-18" "0.9.7e" "OpenSSL" |
| 133 | .SH "NAME" |
| 134 | verify \- Utility to verify certificates. |
| 135 | .SH "SYNOPSIS" |
| 136 | .IX Header "SYNOPSIS" |
| 137 | \&\fBopenssl\fR \fBverify\fR |
| 138 | [\fB\-CApath directory\fR] |
| 139 | [\fB\-CAfile file\fR] |
| 140 | [\fB\-purpose purpose\fR] |
| 141 | [\fB\-untrusted file\fR] |
| 142 | [\fB\-help\fR] |
| 143 | [\fB\-issuer_checks\fR] |
| 144 | [\fB\-verbose\fR] |
| 145 | [\fB\-\fR] |
| 146 | [certificates] |
| 147 | .SH "DESCRIPTION" |
| 148 | .IX Header "DESCRIPTION" |
| 149 | The \fBverify\fR command verifies certificate chains. |
| 150 | .SH "COMMAND OPTIONS" |
| 151 | .IX Header "COMMAND OPTIONS" |
| 152 | .IP "\fB\-CApath directory\fR" 4 |
| 153 | .IX Item "-CApath directory" |
| 154 | A directory of trusted certificates. The certificates should have names |
| 155 | of the form: hash.0 or have symbolic links to them of this |
| 156 | form (\*(L"hash\*(R" is the hashed certificate subject name: see the \fB\-hash\fR option |
| 157 | of the \fBx509\fR utility). Under Unix the \fBc_rehash\fR script will automatically |
| 158 | create symbolic links to a directory of certificates. |
| 159 | .IP "\fB\-CAfile file\fR" 4 |
| 160 | .IX Item "-CAfile file" |
| 161 | A file of trusted certificates. The file should contain multiple certificates |
| 162 | in \s-1PEM\s0 format concatenated together. |
| 163 | .IP "\fB\-untrusted file\fR" 4 |
| 164 | .IX Item "-untrusted file" |
| 165 | A file of untrusted certificates. The file should contain multiple certificates |
| 166 | .IP "\fB\-purpose purpose\fR" 4 |
| 167 | .IX Item "-purpose purpose" |
| 168 | the intended use for the certificate. Without this option no chain verification |
| 169 | will be done. Currently accepted uses are \fBsslclient\fR, \fBsslserver\fR, |
| 170 | \&\fBnssslserver\fR, \fBsmimesign\fR, \fBsmimeencrypt\fR. See the \fB\s-1VERIFY\s0 \s-1OPERATION\s0\fR |
| 171 | section for more information. |
| 172 | .IP "\fB\-help\fR" 4 |
| 173 | .IX Item "-help" |
| 174 | prints out a usage message. |
| 175 | .IP "\fB\-verbose\fR" 4 |
| 176 | .IX Item "-verbose" |
| 177 | print extra information about the operations being performed. |
| 178 | .IP "\fB\-issuer_checks\fR" 4 |
| 179 | .IX Item "-issuer_checks" |
| 180 | print out diagnostics relating to searches for the issuer certificate |
| 181 | of the current certificate. This shows why each candidate issuer |
| 182 | certificate was rejected. However the presence of rejection messages |
| 183 | does not itself imply that anything is wrong: during the normal |
| 184 | verify process several rejections may take place. |
| 185 | .IP "\fB\-\fR" 4 |
| 186 | .IX Item "-" |
| 187 | marks the last option. All arguments following this are assumed to be |
| 188 | certificate files. This is useful if the first certificate filename begins |
| 189 | with a \fB\-\fR. |
| 190 | .IP "\fBcertificates\fR" 4 |
| 191 | .IX Item "certificates" |
| 192 | one or more certificates to verify. If no certificate filenames are included |
| 193 | then an attempt is made to read a certificate from standard input. They should |
| 194 | all be in \s-1PEM\s0 format. |
| 195 | .SH "VERIFY OPERATION" |
| 196 | .IX Header "VERIFY OPERATION" |
| 197 | The \fBverify\fR program uses the same functions as the internal \s-1SSL\s0 and S/MIME |
| 198 | verification, therefore this description applies to these verify operations |
| 199 | too. |
| 200 | .PP |
| 201 | There is one crucial difference between the verify operations performed |
| 202 | by the \fBverify\fR program: wherever possible an attempt is made to continue |
| 203 | after an error whereas normally the verify operation would halt on the |
| 204 | first error. This allows all the problems with a certificate chain to be |
| 205 | determined. |
| 206 | .PP |
| 207 | The verify operation consists of a number of separate steps. |
| 208 | .PP |
| 209 | Firstly a certificate chain is built up starting from the supplied certificate |
| 210 | and ending in the root \s-1CA\s0. It is an error if the whole chain cannot be built |
| 211 | up. The chain is built up by looking up the issuers certificate of the current |
| 212 | certificate. If a certificate is found which is its own issuer it is assumed |
| 213 | to be the root \s-1CA\s0. |
| 214 | .PP |
| 215 | The process of 'looking up the issuers certificate' itself involves a number |
| 216 | of steps. In versions of OpenSSL before 0.9.5a the first certificate whose |
| 217 | subject name matched the issuer of the current certificate was assumed to be |
| 218 | the issuers certificate. In OpenSSL 0.9.6 and later all certificates |
| 219 | whose subject name matches the issuer name of the current certificate are |
| 220 | subject to further tests. The relevant authority key identifier components |
| 221 | of the current certificate (if present) must match the subject key identifier |
| 222 | (if present) and issuer and serial number of the candidate issuer, in addition |
| 223 | the keyUsage extension of the candidate issuer (if present) must permit |
| 224 | certificate signing. |
| 225 | .PP |
| 226 | The lookup first looks in the list of untrusted certificates and if no match |
| 227 | is found the remaining lookups are from the trusted certificates. The root \s-1CA\s0 |
| 228 | is always looked up in the trusted certificate list: if the certificate to |
| 229 | verify is a root certificate then an exact match must be found in the trusted |
| 230 | list. |
| 231 | .PP |
| 232 | The second operation is to check every untrusted certificate's extensions for |
| 233 | consistency with the supplied purpose. If the \fB\-purpose\fR option is not included |
| 234 | then no checks are done. The supplied or \*(L"leaf\*(R" certificate must have extensions |
| 235 | compatible with the supplied purpose and all other certificates must also be valid |
| 236 | \&\s-1CA\s0 certificates. The precise extensions required are described in more detail in |
| 237 | the \fB\s-1CERTIFICATE\s0 \s-1EXTENSIONS\s0\fR section of the \fBx509\fR utility. |
| 238 | .PP |
| 239 | The third operation is to check the trust settings on the root \s-1CA\s0. The root |
| 240 | \&\s-1CA\s0 should be trusted for the supplied purpose. For compatibility with previous |
| 241 | versions of SSLeay and OpenSSL a certificate with no trust settings is considered |
| 242 | to be valid for all purposes. |
| 243 | .PP |
| 244 | The final operation is to check the validity of the certificate chain. The validity |
| 245 | period is checked against the current system time and the notBefore and notAfter |
| 246 | dates in the certificate. The certificate signatures are also checked at this |
| 247 | point. |
| 248 | .PP |
| 249 | If all operations complete successfully then certificate is considered valid. If |
| 250 | any operation fails then the certificate is not valid. |
| 251 | .SH "DIAGNOSTICS" |
| 252 | .IX Header "DIAGNOSTICS" |
| 253 | When a verify operation fails the output messages can be somewhat cryptic. The |
| 254 | general form of the error message is: |
| 255 | .PP |
| 256 | .Vb 2 |
| 257 | \& server.pem: /C=AU/ST=Queensland/O=CryptSoft Pty Ltd/CN=Test CA (1024 bit) |
| 258 | \& error 24 at 1 depth lookup:invalid CA certificate |
| 259 | .Ve |
| 260 | .PP |
| 261 | The first line contains the name of the certificate being verified followed by |
| 262 | the subject name of the certificate. The second line contains the error number |
| 263 | and the depth. The depth is number of the certificate being verified when a |
| 264 | problem was detected starting with zero for the certificate being verified itself |
| 265 | then 1 for the \s-1CA\s0 that signed the certificate and so on. Finally a text version |
| 266 | of the error number is presented. |
| 267 | .PP |
| 268 | An exhaustive list of the error codes and messages is shown below, this also |
| 269 | includes the name of the error code as defined in the header file x509_vfy.h |
| 270 | Some of the error codes are defined but never returned: these are described |
| 271 | as \*(L"unused\*(R". |
| 272 | .IP "\fB0 X509_V_OK: ok\fR" 4 |
| 273 | .IX Item "0 X509_V_OK: ok" |
| 274 | the operation was successful. |
| 275 | .IP "\fB2 X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT: unable to get issuer certificate\fR" 4 |
| 276 | .IX Item "2 X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT: unable to get issuer certificate" |
| 277 | the issuer certificate could not be found: this occurs if the issuer certificate |
| 278 | of an untrusted certificate cannot be found. |
| 279 | .IP "\fB3 X509_V_ERR_UNABLE_TO_GET_CRL unable to get certificate \s-1CRL\s0\fR" 4 |
| 280 | .IX Item "3 X509_V_ERR_UNABLE_TO_GET_CRL unable to get certificate CRL" |
| 281 | the \s-1CRL\s0 of a certificate could not be found. Unused. |
| 282 | .IP "\fB4 X509_V_ERR_UNABLE_TO_DECRYPT_CERT_SIGNATURE: unable to decrypt certificate's signature\fR" 4 |
| 283 | .IX Item "4 X509_V_ERR_UNABLE_TO_DECRYPT_CERT_SIGNATURE: unable to decrypt certificate's signature" |
| 284 | the certificate signature could not be decrypted. This means that the actual signature value |
| 285 | could not be determined rather than it not matching the expected value, this is only |
| 286 | meaningful for \s-1RSA\s0 keys. |
| 287 | .IP "\fB5 X509_V_ERR_UNABLE_TO_DECRYPT_CRL_SIGNATURE: unable to decrypt \s-1CRL\s0's signature\fR" 4 |
| 288 | .IX Item "5 X509_V_ERR_UNABLE_TO_DECRYPT_CRL_SIGNATURE: unable to decrypt CRL's signature" |
| 289 | the \s-1CRL\s0 signature could not be decrypted: this means that the actual signature value |
| 290 | could not be determined rather than it not matching the expected value. Unused. |
| 291 | .IP "\fB6 X509_V_ERR_UNABLE_TO_DECODE_ISSUER_PUBLIC_KEY: unable to decode issuer public key\fR" 4 |
| 292 | .IX Item "6 X509_V_ERR_UNABLE_TO_DECODE_ISSUER_PUBLIC_KEY: unable to decode issuer public key" |
| 293 | the public key in the certificate SubjectPublicKeyInfo could not be read. |
| 294 | .IP "\fB7 X509_V_ERR_CERT_SIGNATURE_FAILURE: certificate signature failure\fR" 4 |
| 295 | .IX Item "7 X509_V_ERR_CERT_SIGNATURE_FAILURE: certificate signature failure" |
| 296 | the signature of the certificate is invalid. |
| 297 | .IP "\fB8 X509_V_ERR_CRL_SIGNATURE_FAILURE: \s-1CRL\s0 signature failure\fR" 4 |
| 298 | .IX Item "8 X509_V_ERR_CRL_SIGNATURE_FAILURE: CRL signature failure" |
| 299 | the signature of the certificate is invalid. Unused. |
| 300 | .IP "\fB9 X509_V_ERR_CERT_NOT_YET_VALID: certificate is not yet valid\fR" 4 |
| 301 | .IX Item "9 X509_V_ERR_CERT_NOT_YET_VALID: certificate is not yet valid" |
| 302 | the certificate is not yet valid: the notBefore date is after the current time. |
| 303 | .IP "\fB10 X509_V_ERR_CERT_HAS_EXPIRED: certificate has expired\fR" 4 |
| 304 | .IX Item "10 X509_V_ERR_CERT_HAS_EXPIRED: certificate has expired" |
| 305 | the certificate has expired: that is the notAfter date is before the current time. |
| 306 | .IP "\fB11 X509_V_ERR_CRL_NOT_YET_VALID: \s-1CRL\s0 is not yet valid\fR" 4 |
| 307 | .IX Item "11 X509_V_ERR_CRL_NOT_YET_VALID: CRL is not yet valid" |
| 308 | the \s-1CRL\s0 is not yet valid. Unused. |
| 309 | .IP "\fB12 X509_V_ERR_CRL_HAS_EXPIRED: \s-1CRL\s0 has expired\fR" 4 |
| 310 | .IX Item "12 X509_V_ERR_CRL_HAS_EXPIRED: CRL has expired" |
| 311 | the \s-1CRL\s0 has expired. Unused. |
| 312 | .IP "\fB13 X509_V_ERR_ERROR_IN_CERT_NOT_BEFORE_FIELD: format error in certificate's notBefore field\fR" 4 |
| 313 | .IX Item "13 X509_V_ERR_ERROR_IN_CERT_NOT_BEFORE_FIELD: format error in certificate's notBefore field" |
| 314 | the certificate notBefore field contains an invalid time. |
| 315 | .IP "\fB14 X509_V_ERR_ERROR_IN_CERT_NOT_AFTER_FIELD: format error in certificate's notAfter field\fR" 4 |
| 316 | .IX Item "14 X509_V_ERR_ERROR_IN_CERT_NOT_AFTER_FIELD: format error in certificate's notAfter field" |
| 317 | the certificate notAfter field contains an invalid time. |
| 318 | .IP "\fB15 X509_V_ERR_ERROR_IN_CRL_LAST_UPDATE_FIELD: format error in \s-1CRL\s0's lastUpdate field\fR" 4 |
| 319 | .IX Item "15 X509_V_ERR_ERROR_IN_CRL_LAST_UPDATE_FIELD: format error in CRL's lastUpdate field" |
| 320 | the \s-1CRL\s0 lastUpdate field contains an invalid time. Unused. |
| 321 | .IP "\fB16 X509_V_ERR_ERROR_IN_CRL_NEXT_UPDATE_FIELD: format error in \s-1CRL\s0's nextUpdate field\fR" 4 |
| 322 | .IX Item "16 X509_V_ERR_ERROR_IN_CRL_NEXT_UPDATE_FIELD: format error in CRL's nextUpdate field" |
| 323 | the \s-1CRL\s0 nextUpdate field contains an invalid time. Unused. |
| 324 | .IP "\fB17 X509_V_ERR_OUT_OF_MEM: out of memory\fR" 4 |
| 325 | .IX Item "17 X509_V_ERR_OUT_OF_MEM: out of memory" |
| 326 | an error occurred trying to allocate memory. This should never happen. |
| 327 | .IP "\fB18 X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT: self signed certificate\fR" 4 |
| 328 | .IX Item "18 X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT: self signed certificate" |
| 329 | the passed certificate is self signed and the same certificate cannot be found in the list of |
| 330 | trusted certificates. |
| 331 | .IP "\fB19 X509_V_ERR_SELF_SIGNED_CERT_IN_CHAIN: self signed certificate in certificate chain\fR" 4 |
| 332 | .IX Item "19 X509_V_ERR_SELF_SIGNED_CERT_IN_CHAIN: self signed certificate in certificate chain" |
| 333 | the certificate chain could be built up using the untrusted certificates but the root could not |
| 334 | be found locally. |
| 335 | .IP "\fB20 X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT_LOCALLY: unable to get local issuer certificate\fR" 4 |
| 336 | .IX Item "20 X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT_LOCALLY: unable to get local issuer certificate" |
| 337 | the issuer certificate of a locally looked up certificate could not be found. This normally means |
| 338 | the list of trusted certificates is not complete. |
| 339 | .IP "\fB21 X509_V_ERR_UNABLE_TO_VERIFY_LEAF_SIGNATURE: unable to verify the first certificate\fR" 4 |
| 340 | .IX Item "21 X509_V_ERR_UNABLE_TO_VERIFY_LEAF_SIGNATURE: unable to verify the first certificate" |
| 341 | no signatures could be verified because the chain contains only one certificate and it is not |
| 342 | self signed. |
| 343 | .IP "\fB22 X509_V_ERR_CERT_CHAIN_TOO_LONG: certificate chain too long\fR" 4 |
| 344 | .IX Item "22 X509_V_ERR_CERT_CHAIN_TOO_LONG: certificate chain too long" |
| 345 | the certificate chain length is greater than the supplied maximum depth. Unused. |
| 346 | .IP "\fB23 X509_V_ERR_CERT_REVOKED: certificate revoked\fR" 4 |
| 347 | .IX Item "23 X509_V_ERR_CERT_REVOKED: certificate revoked" |
| 348 | the certificate has been revoked. Unused. |
| 349 | .IP "\fB24 X509_V_ERR_INVALID_CA: invalid \s-1CA\s0 certificate\fR" 4 |
| 350 | .IX Item "24 X509_V_ERR_INVALID_CA: invalid CA certificate" |
| 351 | a \s-1CA\s0 certificate is invalid. Either it is not a \s-1CA\s0 or its extensions are not consistent |
| 352 | with the supplied purpose. |
| 353 | .IP "\fB25 X509_V_ERR_PATH_LENGTH_EXCEEDED: path length constraint exceeded\fR" 4 |
| 354 | .IX Item "25 X509_V_ERR_PATH_LENGTH_EXCEEDED: path length constraint exceeded" |
| 355 | the basicConstraints pathlength parameter has been exceeded. |
| 356 | .IP "\fB26 X509_V_ERR_INVALID_PURPOSE: unsupported certificate purpose\fR" 4 |
| 357 | .IX Item "26 X509_V_ERR_INVALID_PURPOSE: unsupported certificate purpose" |
| 358 | the supplied certificate cannot be used for the specified purpose. |
| 359 | .IP "\fB27 X509_V_ERR_CERT_UNTRUSTED: certificate not trusted\fR" 4 |
| 360 | .IX Item "27 X509_V_ERR_CERT_UNTRUSTED: certificate not trusted" |
| 361 | the root \s-1CA\s0 is not marked as trusted for the specified purpose. |
| 362 | .IP "\fB28 X509_V_ERR_CERT_REJECTED: certificate rejected\fR" 4 |
| 363 | .IX Item "28 X509_V_ERR_CERT_REJECTED: certificate rejected" |
| 364 | the root \s-1CA\s0 is marked to reject the specified purpose. |
| 365 | .IP "\fB29 X509_V_ERR_SUBJECT_ISSUER_MISMATCH: subject issuer mismatch\fR" 4 |
| 366 | .IX Item "29 X509_V_ERR_SUBJECT_ISSUER_MISMATCH: subject issuer mismatch" |
| 367 | the current candidate issuer certificate was rejected because its subject name |
| 368 | did not match the issuer name of the current certificate. Only displayed when |
| 369 | the \fB\-issuer_checks\fR option is set. |
| 370 | .IP "\fB30 X509_V_ERR_AKID_SKID_MISMATCH: authority and subject key identifier mismatch\fR" 4 |
| 371 | .IX Item "30 X509_V_ERR_AKID_SKID_MISMATCH: authority and subject key identifier mismatch" |
| 372 | the current candidate issuer certificate was rejected because its subject key |
| 373 | identifier was present and did not match the authority key identifier current |
| 374 | certificate. Only displayed when the \fB\-issuer_checks\fR option is set. |
| 375 | .IP "\fB31 X509_V_ERR_AKID_ISSUER_SERIAL_MISMATCH: authority and issuer serial number mismatch\fR" 4 |
| 376 | .IX Item "31 X509_V_ERR_AKID_ISSUER_SERIAL_MISMATCH: authority and issuer serial number mismatch" |
| 377 | the current candidate issuer certificate was rejected because its issuer name |
| 378 | and serial number was present and did not match the authority key identifier |
| 379 | of the current certificate. Only displayed when the \fB\-issuer_checks\fR option is set. |
| 380 | .IP "\fB32 X509_V_ERR_KEYUSAGE_NO_CERTSIGN:key usage does not include certificate signing\fR" 4 |
| 381 | .IX Item "32 X509_V_ERR_KEYUSAGE_NO_CERTSIGN:key usage does not include certificate signing" |
| 382 | the current candidate issuer certificate was rejected because its keyUsage extension |
| 383 | does not permit certificate signing. |
| 384 | .IP "\fB50 X509_V_ERR_APPLICATION_VERIFICATION: application verification failure\fR" 4 |
| 385 | .IX Item "50 X509_V_ERR_APPLICATION_VERIFICATION: application verification failure" |
| 386 | an application specific error. Unused. |
| 387 | .SH "BUGS" |
| 388 | .IX Header "BUGS" |
| 389 | Although the issuer checks are a considerably improvement over the old technique they still |
| 390 | suffer from limitations in the underlying X509_LOOKUP \s-1API\s0. One consequence of this is that |
| 391 | trusted certificates with matching subject name must either appear in a file (as specified by the |
| 392 | \&\fB\-CAfile\fR option) or a directory (as specified by \fB\-CApath\fR. If they occur in both then only |
| 393 | the certificates in the file will be recognised. |
| 394 | .PP |
| 395 | Previous versions of OpenSSL assume certificates with matching subject name are identical and |
| 396 | mishandled them. |
| 397 | .SH "SEE ALSO" |
| 398 | .IX Header "SEE ALSO" |
| 399 | \&\fIx509\fR\|(1) |