| 1 | .rn '' }` |
| 2 | ''' $RCSfile$$Revision$$Date$ |
| 3 | ''' |
| 4 | ''' $Log$ |
| 5 | ''' |
| 6 | .de Sh |
| 7 | .br |
| 8 | .if t .Sp |
| 9 | .ne 5 |
| 10 | .PP |
| 11 | \fB\\$1\fR |
| 12 | .PP |
| 13 | .. |
| 14 | .de Sp |
| 15 | .if t .sp .5v |
| 16 | .if n .sp |
| 17 | .. |
| 18 | .de Ip |
| 19 | .br |
| 20 | .ie \\n(.$>=3 .ne \\$3 |
| 21 | .el .ne 3 |
| 22 | .IP "\\$1" \\$2 |
| 23 | .. |
| 24 | .de Vb |
| 25 | .ft CW |
| 26 | .nf |
| 27 | .ne \\$1 |
| 28 | .. |
| 29 | .de Ve |
| 30 | .ft R |
| 31 | |
| 32 | .fi |
| 33 | .. |
| 34 | ''' |
| 35 | ''' |
| 36 | ''' Set up \*(-- to give an unbreakable dash; |
| 37 | ''' string Tr holds user defined translation string. |
| 38 | ''' Bell System Logo is used as a dummy character. |
| 39 | ''' |
| 40 | .tr \(*W-|\(bv\*(Tr |
| 41 | .ie n \{\ |
| 42 | .ds -- \(*W- |
| 43 | .ds PI pi |
| 44 | .if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch |
| 45 | .if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch |
| 46 | .ds L" "" |
| 47 | .ds R" "" |
| 48 | ''' \*(M", \*(S", \*(N" and \*(T" are the equivalent of |
| 49 | ''' \*(L" and \*(R", except that they are used on ".xx" lines, |
| 50 | ''' such as .IP and .SH, which do another additional levels of |
| 51 | ''' double-quote interpretation |
| 52 | .ds M" """ |
| 53 | .ds S" """ |
| 54 | .ds N" """"" |
| 55 | .ds T" """"" |
| 56 | .ds L' ' |
| 57 | .ds R' ' |
| 58 | .ds M' ' |
| 59 | .ds S' ' |
| 60 | .ds N' ' |
| 61 | .ds T' ' |
| 62 | 'br\} |
| 63 | .el\{\ |
| 64 | .ds -- \(em\| |
| 65 | .tr \*(Tr |
| 66 | .ds L" `` |
| 67 | .ds R" '' |
| 68 | .ds M" `` |
| 69 | .ds S" '' |
| 70 | .ds N" `` |
| 71 | .ds T" '' |
| 72 | .ds L' ` |
| 73 | .ds R' ' |
| 74 | .ds M' ` |
| 75 | .ds S' ' |
| 76 | .ds N' ` |
| 77 | .ds T' ' |
| 78 | .ds PI \(*p |
| 79 | 'br\} |
| 80 | .\" If the F register is turned on, we'll generate |
| 81 | .\" index entries out stderr for the following things: |
| 82 | .\" TH Title |
| 83 | .\" SH Header |
| 84 | .\" Sh Subsection |
| 85 | .\" Ip Item |
| 86 | .\" X<> Xref (embedded |
| 87 | .\" Of course, you have to process the output yourself |
| 88 | .\" in some meaninful fashion. |
| 89 | .if \nF \{ |
| 90 | .de IX |
| 91 | .tm Index:\\$1\t\\n%\t"\\$2" |
| 92 | .. |
| 93 | .nr % 0 |
| 94 | .rr F |
| 95 | .\} |
| 96 | .TH OCSP 1 "0.9.7d" "2/Sep/2004" "OpenSSL" |
| 97 | .UC |
| 98 | .if n .hy 0 |
| 99 | .if n .na |
| 100 | .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' |
| 101 | .de CQ \" put $1 in typewriter font |
| 102 | .ft CW |
| 103 | 'if n "\c |
| 104 | 'if t \\&\\$1\c |
| 105 | 'if n \\&\\$1\c |
| 106 | 'if n \&" |
| 107 | \\&\\$2 \\$3 \\$4 \\$5 \\$6 \\$7 |
| 108 | '.ft R |
| 109 | .. |
| 110 | .\" @(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2 |
| 111 | . \" AM - accent mark definitions |
| 112 | .bd B 3 |
| 113 | . \" fudge factors for nroff and troff |
| 114 | .if n \{\ |
| 115 | . ds #H 0 |
| 116 | . ds #V .8m |
| 117 | . ds #F .3m |
| 118 | . ds #[ \f1 |
| 119 | . ds #] \fP |
| 120 | .\} |
| 121 | .if t \{\ |
| 122 | . ds #H ((1u-(\\\\n(.fu%2u))*.13m) |
| 123 | . ds #V .6m |
| 124 | . ds #F 0 |
| 125 | . ds #[ \& |
| 126 | . ds #] \& |
| 127 | .\} |
| 128 | . \" simple accents for nroff and troff |
| 129 | .if n \{\ |
| 130 | . ds ' \& |
| 131 | . ds ` \& |
| 132 | . ds ^ \& |
| 133 | . ds , \& |
| 134 | . ds ~ ~ |
| 135 | . ds ? ? |
| 136 | . ds ! ! |
| 137 | . ds / |
| 138 | . ds q |
| 139 | .\} |
| 140 | .if t \{\ |
| 141 | . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" |
| 142 | . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' |
| 143 | . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' |
| 144 | . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' |
| 145 | . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' |
| 146 | . ds ? \s-2c\h'-\w'c'u*7/10'\u\h'\*(#H'\zi\d\s+2\h'\w'c'u*8/10' |
| 147 | . ds ! \s-2\(or\s+2\h'-\w'\(or'u'\v'-.8m'.\v'.8m' |
| 148 | . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' |
| 149 | . ds q o\h'-\w'o'u*8/10'\s-4\v'.4m'\z\(*i\v'-.4m'\s+4\h'\w'o'u*8/10' |
| 150 | .\} |
| 151 | . \" troff and (daisy-wheel) nroff accents |
| 152 | .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V' |
| 153 | .ds 8 \h'\*(#H'\(*b\h'-\*(#H' |
| 154 | .ds v \\k:\h'-(\\n(.wu*9/10-\*(#H)'\v'-\*(#V'\*(#[\s-4v\s0\v'\*(#V'\h'|\\n:u'\*(#] |
| 155 | .ds _ \\k:\h'-(\\n(.wu*9/10-\*(#H+(\*(#F*2/3))'\v'-.4m'\z\(hy\v'.4m'\h'|\\n:u' |
| 156 | .ds . \\k:\h'-(\\n(.wu*8/10)'\v'\*(#V*4/10'\z.\v'-\*(#V*4/10'\h'|\\n:u' |
| 157 | .ds 3 \*(#[\v'.2m'\s-2\&3\s0\v'-.2m'\*(#] |
| 158 | .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#] |
| 159 | .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H' |
| 160 | .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u' |
| 161 | .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#] |
| 162 | .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#] |
| 163 | .ds ae a\h'-(\w'a'u*4/10)'e |
| 164 | .ds Ae A\h'-(\w'A'u*4/10)'E |
| 165 | .ds oe o\h'-(\w'o'u*4/10)'e |
| 166 | .ds Oe O\h'-(\w'O'u*4/10)'E |
| 167 | . \" corrections for vroff |
| 168 | .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u' |
| 169 | .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u' |
| 170 | . \" for low resolution devices (crt and lpr) |
| 171 | .if \n(.H>23 .if \n(.V>19 \ |
| 172 | \{\ |
| 173 | . ds : e |
| 174 | . ds 8 ss |
| 175 | . ds v \h'-1'\o'\(aa\(ga' |
| 176 | . ds _ \h'-1'^ |
| 177 | . ds . \h'-1'. |
| 178 | . ds 3 3 |
| 179 | . ds o a |
| 180 | . ds d- d\h'-1'\(ga |
| 181 | . ds D- D\h'-1'\(hy |
| 182 | . ds th \o'bp' |
| 183 | . ds Th \o'LP' |
| 184 | . ds ae ae |
| 185 | . ds Ae AE |
| 186 | . ds oe oe |
| 187 | . ds Oe OE |
| 188 | .\} |
| 189 | .rm #[ #] #H #V #F C |
| 190 | .SH "NAME" |
| 191 | ocsp \- Online Certificate Status Protocol utility |
| 192 | .SH "SYNOPSIS" |
| 193 | \fBopenssl\fR \fBocsp\fR |
| 194 | [\fB\-out file\fR] |
| 195 | [\fB\-issuer file\fR] |
| 196 | [\fB\-cert file\fR] |
| 197 | [\fB\-serial n\fR] |
| 198 | [\fB\-signer file\fR] |
| 199 | [\fB\-signkey file\fR] |
| 200 | [\fB\-sign_other file\fR] |
| 201 | [\fB\-no_certs\fR] |
| 202 | [\fB\-req_text\fR] |
| 203 | [\fB\-resp_text\fR] |
| 204 | [\fB\-text\fR] |
| 205 | [\fB\-reqout file\fR] |
| 206 | [\fB\-respout file\fR] |
| 207 | [\fB\-reqin file\fR] |
| 208 | [\fB\-respin file\fR] |
| 209 | [\fB\-nonce\fR] |
| 210 | [\fB\-no_nonce\fR] |
| 211 | [\fB\-url URL\fR] |
| 212 | [\fB\-host host:n\fR] |
| 213 | [\fB\-path\fR] |
| 214 | [\fB\-CApath dir\fR] |
| 215 | [\fB\-CAfile file\fR] |
| 216 | [\fB\-VAfile file\fR] |
| 217 | [\fB\-validity_period n\fR] |
| 218 | [\fB\-status_age n\fR] |
| 219 | [\fB\-noverify\fR] |
| 220 | [\fB\-verify_other file\fR] |
| 221 | [\fB\-trust_other\fR] |
| 222 | [\fB\-no_intern\fR] |
| 223 | [\fB\-no_signature_verify\fR] |
| 224 | [\fB\-no_cert_verify\fR] |
| 225 | [\fB\-no_chain\fR] |
| 226 | [\fB\-no_cert_checks\fR] |
| 227 | [\fB\-port num\fR] |
| 228 | [\fB\-index file\fR] |
| 229 | [\fB\-CA file\fR] |
| 230 | [\fB\-rsigner file\fR] |
| 231 | [\fB\-rkey file\fR] |
| 232 | [\fB\-rother file\fR] |
| 233 | [\fB\-resp_no_certs\fR] |
| 234 | [\fB\-nmin n\fR] |
| 235 | [\fB\-ndays n\fR] |
| 236 | [\fB\-resp_key_id\fR] |
| 237 | [\fB\-nrequest n\fR] |
| 238 | .SH "DESCRIPTION" |
| 239 | The Online Certificate Status Protocol (OCSP) enables applications to |
| 240 | determine the (revocation) state of an identified certificate (RFC 2560). |
| 241 | .PP |
| 242 | The \fBocsp\fR command performs many common OCSP tasks. It can be used |
| 243 | to print out requests and responses, create requests and send queries |
| 244 | to an OCSP responder and behave like a mini OCSP server itself. |
| 245 | .SH "OCSP CLIENT OPTIONS" |
| 246 | .Ip "\fB\-out filename\fR" 4 |
| 247 | specify output filename, default is standard output. |
| 248 | .Ip "\fB\-issuer filename\fR" 4 |
| 249 | This specifies the current issuer certificate. This option can be used |
| 250 | multiple times. The certificate specified in \fBfilename\fR must be in |
| 251 | \s-1PEM\s0 format. |
| 252 | .Ip "\fB\-cert filename\fR" 4 |
| 253 | Add the certificate \fBfilename\fR to the request. The issuer certificate |
| 254 | is taken from the previous \fBissuer\fR option, or an error occurs if no |
| 255 | issuer certificate is specified. |
| 256 | .Ip "\fB\-serial num\fR" 4 |
| 257 | Same as the \fBcert\fR option except the certificate with serial number |
| 258 | \fBnum\fR is added to the request. The serial number is interpreted as a |
| 259 | decimal integer unless preceded by \fB0x\fR. Negative integers can also |
| 260 | be specified by preceding the value by a \fB\-\fR sign. |
| 261 | .Ip "\fB\-signer filename\fR, \fB\-signkey filename\fR" 4 |
| 262 | Sign the \s-1OCSP\s0 request using the certificate specified in the \fBsigner\fR |
| 263 | option and the private key specified by the \fBsignkey\fR option. If |
| 264 | the \fBsignkey\fR option is not present then the private key is read |
| 265 | from the same file as the certificate. If neither option is specified then |
| 266 | the \s-1OCSP\s0 request is not signed. |
| 267 | .Ip "\fB\-sign_other filename\fR" 4 |
| 268 | Additional certificates to include in the signed request. |
| 269 | .Ip "\fB\-nonce\fR, \fB\-no_nonce\fR" 4 |
| 270 | Add an \s-1OCSP\s0 nonce extension to a request or disable \s-1OCSP\s0 nonce addition. |
| 271 | Normally if an \s-1OCSP\s0 request is input using the \fBrespin\fR option no |
| 272 | nonce is added: using the \fBnonce\fR option will force addition of a nonce. |
| 273 | If an \s-1OCSP\s0 request is being created (using \fBcert\fR and \fBserial\fR options) |
| 274 | a nonce is automatically added specifying \fBno_nonce\fR overrides this. |
| 275 | .Ip "\fB\-req_text\fR, \fB\-resp_text\fR, \fB\-text\fR" 4 |
| 276 | print out the text form of the \s-1OCSP\s0 request, response or both respectively. |
| 277 | .Ip "\fB\-reqout file\fR, \fB\-respout file\fR" 4 |
| 278 | write out the \s-1DER\s0 encoded certificate request or response to \fBfile\fR. |
| 279 | .Ip "\fB\-reqin file\fR, \fB\-respin file\fR" 4 |
| 280 | read \s-1OCSP\s0 request or response file from \fBfile\fR. These option are ignored |
| 281 | if \s-1OCSP\s0 request or response creation is implied by other options (for example |
| 282 | with \fBserial\fR, \fBcert\fR and \fBhost\fR options). |
| 283 | .Ip "\fB\-url responder_url\fR" 4 |
| 284 | specify the responder \s-1URL\s0. Both \s-1HTTP\s0 and \s-1HTTPS\s0 (\s-1SSL/TLS\s0) URLs can be specified. |
| 285 | .Ip "\fB\-host hostname:port\fR, \fB\-path pathname\fR" 4 |
| 286 | if the \fBhost\fR option is present then the \s-1OCSP\s0 request is sent to the host |
| 287 | \fBhostname\fR on port \fBport\fR. \fBpath\fR specifies the \s-1HTTP\s0 path name to use |
| 288 | or \*(L"/\*(R" by default. |
| 289 | .Ip "\fB\-CAfile file\fR, \fB\-CApath pathname\fR" 4 |
| 290 | file or pathname containing trusted \s-1CA\s0 certificates. These are used to verify |
| 291 | the signature on the \s-1OCSP\s0 response. |
| 292 | .Ip "\fB\-verify_other file\fR" 4 |
| 293 | file containing additional certificates to search when attempting to locate |
| 294 | the \s-1OCSP\s0 response signing certificate. Some responders omit the actual signer's |
| 295 | certificate from the response: this option can be used to supply the necessary |
| 296 | certificate in such cases. |
| 297 | .Ip "\fB\-trust_other\fR" 4 |
| 298 | the certificates specified by the \fB\-verify_certs\fR option should be explicitly |
| 299 | trusted and no additional checks will be performed on them. This is useful |
| 300 | when the complete responder certificate chain is not available or trusting a |
| 301 | root \s-1CA\s0 is not appropriate. |
| 302 | .Ip "\fB\-VAfile file\fR" 4 |
| 303 | file containing explicitly trusted responder certificates. Equivalent to the |
| 304 | \fB\-verify_certs\fR and \fB\-trust_other\fR options. |
| 305 | .Ip "\fB\-noverify\fR" 4 |
| 306 | don't attempt to verify the \s-1OCSP\s0 response signature or the nonce values. This |
| 307 | option will normally only be used for debugging since it disables all verification |
| 308 | of the responders certificate. |
| 309 | .Ip "\fB\-no_intern\fR" 4 |
| 310 | ignore certificates contained in the \s-1OCSP\s0 response when searching for the |
| 311 | signers certificate. With this option the signers certificate must be specified |
| 312 | with either the \fB\-verify_certs\fR or \fB\-VAfile\fR options. |
| 313 | .Ip "\fB\-no_signature_verify\fR" 4 |
| 314 | don't check the signature on the \s-1OCSP\s0 response. Since this option tolerates invalid |
| 315 | signatures on \s-1OCSP\s0 responses it will normally only be used for testing purposes. |
| 316 | .Ip "\fB\-no_cert_verify\fR" 4 |
| 317 | don't verify the \s-1OCSP\s0 response signers certificate at all. Since this option allows |
| 318 | the \s-1OCSP\s0 response to be signed by any certificate it should only be used for |
| 319 | testing purposes. |
| 320 | .Ip "\fB\-no_chain\fR" 4 |
| 321 | do not use certificates in the response as additional untrusted \s-1CA\s0 |
| 322 | certificates. |
| 323 | .Ip "\fB\-no_cert_checks\fR" 4 |
| 324 | don't perform any additional checks on the \s-1OCSP\s0 response signers certificate. |
| 325 | That is do not make any checks to see if the signers certificate is authorised |
| 326 | to provide the necessary status information: as a result this option should |
| 327 | only be used for testing purposes. |
| 328 | .Ip "\fB\-validity_period nsec\fR, \fB\-status_age age\fR" 4 |
| 329 | these options specify the range of times, in seconds, which will be tolerated |
| 330 | in an \s-1OCSP\s0 response. Each certificate status response includes a \fBnotBefore\fR time and |
| 331 | an optional \fBnotAfter\fR time. The current time should fall between these two values, but |
| 332 | the interval between the two times may be only a few seconds. In practice the \s-1OCSP\s0 |
| 333 | responder and clients clocks may not be precisely synchronised and so such a check |
| 334 | may fail. To avoid this the \fB\-validity_period\fR option can be used to specify an |
| 335 | acceptable error range in seconds, the default value is 5 minutes. |
| 336 | .Sp |
| 337 | If the \fBnotAfter\fR time is omitted from a response then this means that new status |
| 338 | information is immediately available. In this case the age of the \fBnotBefore\fR field |
| 339 | is checked to see it is not older than \fBage\fR seconds old. By default this additional |
| 340 | check is not performed. |
| 341 | .SH "OCSP SERVER OPTIONS" |
| 342 | .Ip "\fB\-index indexfile\fR" 4 |
| 343 | \fBindexfile\fR is a text index file in \fBca\fR format containing certificate revocation |
| 344 | information. |
| 345 | .Sp |
| 346 | If the \fBindex\fR option is specified the \fBocsp\fR utility is in responder mode, otherwise |
| 347 | it is in client mode. The \fIrequest\fR\|(s) the responder processes can be either specified on |
| 348 | the command line (using \fBissuer\fR and \fBserial\fR options), supplied in a file (using the |
| 349 | \fBrespin\fR option) or via external \s-1OCSP\s0 clients (if \fBport\fR or \fBurl\fR is specified). |
| 350 | .Sp |
| 351 | If the \fBindex\fR option is present then the \fB\s-1CA\s0\fR and \fBrsigner\fR options must also be |
| 352 | present. |
| 353 | .Ip "\fB\-\s-1CA\s0 file\fR" 4 |
| 354 | \s-1CA\s0 certificate corresponding to the revocation information in \fBindexfile\fR. |
| 355 | .Ip "\fB\-rsigner file\fR" 4 |
| 356 | The certificate to sign \s-1OCSP\s0 responses with. |
| 357 | .Ip "\fB\-rother file\fR" 4 |
| 358 | Additional certificates to include in the \s-1OCSP\s0 response. |
| 359 | .Ip "\fB\-resp_no_certs\fR" 4 |
| 360 | Don't include any certificates in the \s-1OCSP\s0 response. |
| 361 | .Ip "\fB\-resp_key_id\fR" 4 |
| 362 | Identify the signer certificate using the key \s-1ID\s0, default is to use the subject name. |
| 363 | .Ip "\fB\-rkey file\fR" 4 |
| 364 | The private key to sign \s-1OCSP\s0 responses with: if not present the file specified in the |
| 365 | \fBrsigner\fR option is used. |
| 366 | .Ip "\fB\-port portnum\fR" 4 |
| 367 | Port to listen for \s-1OCSP\s0 requests on. The port may also be specified using the \fBurl\fR |
| 368 | option. |
| 369 | .Ip "\fB\-nrequest number\fR" 4 |
| 370 | The \s-1OCSP\s0 server will exit after receiving \fBnumber\fR requests, default unlimited. |
| 371 | .Ip "\fB\-nmin minutes\fR, \fB\-ndays days\fR" 4 |
| 372 | Number of minutes or days when fresh revocation information is available: used in the |
| 373 | \fBnextUpdate\fR field. If neither option is present then the \fBnextUpdate\fR field is |
| 374 | omitted meaning fresh revocation information is immediately available. |
| 375 | .SH "OCSP Response verification." |
| 376 | OCSP Response follows the rules specified in RFC2560. |
| 377 | .PP |
| 378 | Initially the OCSP responder certificate is located and the signature on |
| 379 | the OCSP request checked using the responder certificate's public key. |
| 380 | .PP |
| 381 | Then a normal certificate verify is performed on the OCSP responder certificate |
| 382 | building up a certificate chain in the process. The locations of the trusted |
| 383 | certificates used to build the chain can be specified by the \fBCAfile\fR |
| 384 | and \fBCApath\fR options or they will be looked for in the standard OpenSSL |
| 385 | certificates directory. |
| 386 | .PP |
| 387 | If the initial verify fails then the OCSP verify process halts with an |
| 388 | error. |
| 389 | .PP |
| 390 | Otherwise the issuing CA certificate in the request is compared to the OCSP |
| 391 | responder certificate: if there is a match then the OCSP verify succeeds. |
| 392 | .PP |
| 393 | Otherwise the OCSP responder certificate's CA is checked against the issuing |
| 394 | CA certificate in the request. If there is a match and the OCSPSigning |
| 395 | extended key usage is present in the OCSP responder certificate then the |
| 396 | OCSP verify succeeds. |
| 397 | .PP |
| 398 | Otherwise the root CA of the OCSP responders CA is checked to see if it |
| 399 | is trusted for OCSP signing. If it is the OCSP verify succeeds. |
| 400 | .PP |
| 401 | If none of these checks is successful then the OCSP verify fails. |
| 402 | .PP |
| 403 | What this effectively means if that if the OCSP responder certificate is |
| 404 | authorised directly by the CA it is issuing revocation information about |
| 405 | (and it is correctly configured) then verification will succeed. |
| 406 | .PP |
| 407 | If the OCSP responder is a \*(L"global responder\*(R" which can give details about |
| 408 | multiple CAs and has its own separate certificate chain then its root |
| 409 | CA can be trusted for OCSP signing. For example: |
| 410 | .PP |
| 411 | .Vb 1 |
| 412 | \& openssl x509 -in ocspCA.pem -addtrust OCSPSigning -out trustedCA.pem |
| 413 | .Ve |
| 414 | Alternatively the responder certificate itself can be explicitly trusted |
| 415 | with the \fB\-VAfile\fR option. |
| 416 | .SH "NOTES" |
| 417 | As noted, most of the verify options are for testing or debugging purposes. |
| 418 | Normally only the \fB\-CApath\fR, \fB\-CAfile\fR and (if the responder is a \*(L'global |
| 419 | VA') \fB\-VAfile\fR options need to be used. |
| 420 | .PP |
| 421 | The OCSP server is only useful for test and demonstration purposes: it is |
| 422 | not really usable as a full OCSP responder. It contains only a very |
| 423 | simple HTTP request handling and can only handle the POST form of OCSP |
| 424 | queries. It also handles requests serially meaning it cannot respond to |
| 425 | new requests until it has processed the current one. The text index file |
| 426 | format of revocation is also inefficient for large quantities of revocation |
| 427 | data. |
| 428 | .PP |
| 429 | It is possible to run the \fBocsp\fR application in responder mode via a CGI |
| 430 | script using the \fBrespin\fR and \fBrespout\fR options. |
| 431 | .SH "EXAMPLES" |
| 432 | Create an OCSP request and write it to a file: |
| 433 | .PP |
| 434 | .Vb 1 |
| 435 | \& openssl ocsp -issuer issuer.pem -cert c1.pem -cert c2.pem -reqout req.der |
| 436 | .Ve |
| 437 | Send a query to an OCSP responder with URL http://ocsp.myhost.com/ save the |
| 438 | response to a file and print it out in text form |
| 439 | .PP |
| 440 | .Vb 2 |
| 441 | \& openssl ocsp -issuer issuer.pem -cert c1.pem -cert c2.pem \e |
| 442 | \& -url http://ocsp.myhost.com/ -resp_text -respout resp.der |
| 443 | .Ve |
| 444 | Read in an OCSP response and print out text form: |
| 445 | .PP |
| 446 | .Vb 1 |
| 447 | \& openssl ocsp -respin resp.der -text |
| 448 | .Ve |
| 449 | OCSP server on port 8888 using a standard \fBca\fR configuration, and a separate |
| 450 | responder certificate. All requests and responses are printed to a file. |
| 451 | .PP |
| 452 | .Vb 2 |
| 453 | \& openssl ocsp -index demoCA/index.txt -port 8888 -rsigner rcert.pem -CA demoCA/cacert.pem |
| 454 | \& -text -out log.txt |
| 455 | .Ve |
| 456 | As above but exit after processing one request: |
| 457 | .PP |
| 458 | .Vb 2 |
| 459 | \& openssl ocsp -index demoCA/index.txt -port 8888 -rsigner rcert.pem -CA demoCA/cacert.pem |
| 460 | \& -nrequest 1 |
| 461 | .Ve |
| 462 | Query status information using internally generated request: |
| 463 | .PP |
| 464 | .Vb 2 |
| 465 | \& openssl ocsp -index demoCA/index.txt -rsigner rcert.pem -CA demoCA/cacert.pem |
| 466 | \& -issuer demoCA/cacert.pem -serial 1 |
| 467 | .Ve |
| 468 | Query status information using request read from a file, write response to a |
| 469 | second file. |
| 470 | .PP |
| 471 | .Vb 2 |
| 472 | \& openssl ocsp -index demoCA/index.txt -rsigner rcert.pem -CA demoCA/cacert.pem |
| 473 | \& -reqin req.der -respout resp.der |
| 474 | .Ve |
| 475 | |
| 476 | .rn }` '' |
| 477 | .IX Title "OCSP 1" |
| 478 | .IX Name "ocsp - Online Certificate Status Protocol utility" |
| 479 | |
| 480 | .IX Header "NAME" |
| 481 | |
| 482 | .IX Header "SYNOPSIS" |
| 483 | |
| 484 | .IX Header "DESCRIPTION" |
| 485 | |
| 486 | .IX Header "OCSP CLIENT OPTIONS" |
| 487 | |
| 488 | .IX Item "\fB\-out filename\fR" |
| 489 | |
| 490 | .IX Item "\fB\-issuer filename\fR" |
| 491 | |
| 492 | .IX Item "\fB\-cert filename\fR" |
| 493 | |
| 494 | .IX Item "\fB\-serial num\fR" |
| 495 | |
| 496 | .IX Item "\fB\-signer filename\fR, \fB\-signkey filename\fR" |
| 497 | |
| 498 | .IX Item "\fB\-sign_other filename\fR" |
| 499 | |
| 500 | .IX Item "\fB\-nonce\fR, \fB\-no_nonce\fR" |
| 501 | |
| 502 | .IX Item "\fB\-req_text\fR, \fB\-resp_text\fR, \fB\-text\fR" |
| 503 | |
| 504 | .IX Item "\fB\-reqout file\fR, \fB\-respout file\fR" |
| 505 | |
| 506 | .IX Item "\fB\-reqin file\fR, \fB\-respin file\fR" |
| 507 | |
| 508 | .IX Item "\fB\-url responder_url\fR" |
| 509 | |
| 510 | .IX Item "\fB\-host hostname:port\fR, \fB\-path pathname\fR" |
| 511 | |
| 512 | .IX Item "\fB\-CAfile file\fR, \fB\-CApath pathname\fR" |
| 513 | |
| 514 | .IX Item "\fB\-verify_other file\fR" |
| 515 | |
| 516 | .IX Item "\fB\-trust_other\fR" |
| 517 | |
| 518 | .IX Item "\fB\-VAfile file\fR" |
| 519 | |
| 520 | .IX Item "\fB\-noverify\fR" |
| 521 | |
| 522 | .IX Item "\fB\-no_intern\fR" |
| 523 | |
| 524 | .IX Item "\fB\-no_signature_verify\fR" |
| 525 | |
| 526 | .IX Item "\fB\-no_cert_verify\fR" |
| 527 | |
| 528 | .IX Item "\fB\-no_chain\fR" |
| 529 | |
| 530 | .IX Item "\fB\-no_cert_checks\fR" |
| 531 | |
| 532 | .IX Item "\fB\-validity_period nsec\fR, \fB\-status_age age\fR" |
| 533 | |
| 534 | .IX Header "OCSP SERVER OPTIONS" |
| 535 | |
| 536 | .IX Item "\fB\-index indexfile\fR" |
| 537 | |
| 538 | .IX Item "\fB\-\s-1CA\s0 file\fR" |
| 539 | |
| 540 | .IX Item "\fB\-rsigner file\fR" |
| 541 | |
| 542 | .IX Item "\fB\-rother file\fR" |
| 543 | |
| 544 | .IX Item "\fB\-resp_no_certs\fR" |
| 545 | |
| 546 | .IX Item "\fB\-resp_key_id\fR" |
| 547 | |
| 548 | .IX Item "\fB\-rkey file\fR" |
| 549 | |
| 550 | .IX Item "\fB\-port portnum\fR" |
| 551 | |
| 552 | .IX Item "\fB\-nrequest number\fR" |
| 553 | |
| 554 | .IX Item "\fB\-nmin minutes\fR, \fB\-ndays days\fR" |
| 555 | |
| 556 | .IX Header "OCSP Response verification." |
| 557 | |
| 558 | .IX Header "NOTES" |
| 559 | |
| 560 | .IX Header "EXAMPLES" |
| 561 | |