openssl-ocsp.pod.in 16 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494
  1. =pod
  2. {- OpenSSL::safe::output_do_not_edit_headers(); -}
  3. =head1 NAME
  4. openssl-ocsp - Online Certificate Status Protocol command
  5. =head1 SYNOPSIS
  6. =head2 OCSP Client
  7. B<openssl> B<ocsp>
  8. [B<-help>]
  9. [B<-out> I<file>]
  10. [B<-issuer> I<file>]
  11. [B<-cert> I<file>]
  12. [B<-serial> I<n>]
  13. [B<-signer> I<file>]
  14. [B<-signkey> I<file>]
  15. [B<-sign_other> I<file>]
  16. [B<-nonce>]
  17. [B<-no_nonce>]
  18. [B<-req_text>]
  19. [B<-resp_text>]
  20. [B<-text>]
  21. [B<-no_certs>]
  22. [B<-reqout> I<file>]
  23. [B<-respout> I<file>]
  24. [B<-reqin> I<file>]
  25. [B<-respin> I<file>]
  26. [B<-url> I<URL>]
  27. [B<-host> I<host>:I<port>]
  28. [B<-header>]
  29. [B<-timeout> I<seconds>]
  30. [B<-path>]
  31. [B<-VAfile> I<file>]
  32. [B<-validity_period> I<n>]
  33. [B<-status_age> I<n>]
  34. [B<-noverify>]
  35. [B<-verify_other> I<file>]
  36. [B<-trust_other>]
  37. [B<-no_intern>]
  38. [B<-no_signature_verify>]
  39. [B<-no_cert_verify>]
  40. [B<-no_chain>]
  41. [B<-no_cert_checks>]
  42. [B<-no_explicit>]
  43. [B<-port> I<num>]
  44. [B<-ignore_err>]
  45. =head2 OCSP Server
  46. B<openssl> B<ocsp>
  47. [B<-index> I<file>]
  48. [B<-CA> I<file>]
  49. [B<-rsigner> I<file>]
  50. [B<-rkey> I<file>]
  51. [B<-passin> I<arg>]
  52. [B<-rother> I<file>]
  53. [B<-rsigopt> I<nm>:I<v>]
  54. [B<-rmd> I<digest>]
  55. [B<-badsig>]
  56. [B<-resp_no_certs>]
  57. [B<-nmin> I<n>]
  58. [B<-ndays> I<n>]
  59. [B<-resp_key_id>]
  60. [B<-nrequest> I<n>]
  61. [B<-multi> I<process-count>]
  62. [B<-rcid> I<digest>]
  63. [B<-I<digest>>]
  64. {- $OpenSSL::safe::opt_trust_synopsis -}
  65. {- $OpenSSL::safe::opt_v_synopsis -}
  66. {- $OpenSSL::safe::opt_provider_synopsis -}
  67. =for openssl ifdef multi
  68. =head1 DESCRIPTION
  69. The Online Certificate Status Protocol (OCSP) enables applications to
  70. determine the (revocation) state of an identified certificate (RFC 2560).
  71. This command performs many common OCSP tasks. It can be used
  72. to print out requests and responses, create requests and send queries
  73. to an OCSP responder and behave like a mini OCSP server itself.
  74. =head1 OPTIONS
  75. This command operates as either a client or a server.
  76. The options are described below, divided into those two modes.
  77. =head2 OCSP Client Options
  78. =over 4
  79. =item B<-help>
  80. Print out a usage message.
  81. =item B<-out> I<filename>
  82. specify output filename, default is standard output.
  83. =item B<-issuer> I<filename>
  84. This specifies the current issuer certificate. This option can be used
  85. multiple times.
  86. This option B<MUST> come before any B<-cert> options.
  87. =item B<-cert> I<filename>
  88. Add the certificate I<filename> to the request. The issuer certificate
  89. is taken from the previous B<-issuer> option, or an error occurs if no
  90. issuer certificate is specified.
  91. =item B<-serial> I<num>
  92. Same as the B<-cert> option except the certificate with serial number
  93. B<num> is added to the request. The serial number is interpreted as a
  94. decimal integer unless preceded by C<0x>. Negative integers can also
  95. be specified by preceding the value by a C<-> sign.
  96. =item B<-signer> I<filename>, B<-signkey> I<filename>
  97. Sign the OCSP request using the certificate specified in the B<-signer>
  98. option and the private key specified by the B<-signkey> option. If
  99. the B<-signkey> option is not present then the private key is read
  100. from the same file as the certificate. If neither option is specified then
  101. the OCSP request is not signed.
  102. =item B<-sign_other> I<filename>
  103. Additional certificates to include in the signed request.
  104. The input can be in PEM, DER, or PKCS#12 format.
  105. =item B<-nonce>, B<-no_nonce>
  106. Add an OCSP nonce extension to a request or disable OCSP nonce addition.
  107. Normally if an OCSP request is input using the B<-reqin> option no
  108. nonce is added: using the B<-nonce> option will force addition of a nonce.
  109. If an OCSP request is being created (using B<-cert> and B<-serial> options)
  110. a nonce is automatically added specifying B<-no_nonce> overrides this.
  111. =item B<-req_text>, B<-resp_text>, B<-text>
  112. Print out the text form of the OCSP request, response or both respectively.
  113. =item B<-reqout> I<file>, B<-respout> I<file>
  114. Write out the DER encoded certificate request or response to I<file>.
  115. =item B<-reqin> I<file>, B<-respin> I<file>
  116. Read OCSP request or response file from I<file>. These option are ignored
  117. if OCSP request or response creation is implied by other options (for example
  118. with B<-serial>, B<-cert> and B<-host> options).
  119. =item B<-url> I<responder_url>
  120. Specify the responder URL. Both HTTP and HTTPS (SSL/TLS) URLs can be specified.
  121. =item B<-host> I<hostname>:I<port>, B<-path> I<pathname>
  122. If the B<-host> option is present then the OCSP request is sent to the host
  123. I<hostname> on port I<port>. The B<-path> option specifies the HTTP pathname
  124. to use or "/" by default. This is equivalent to specifying B<-url> with scheme
  125. http:// and the given hostname, port, and pathname.
  126. =item B<-header> I<name>=I<value>
  127. Adds the header I<name> with the specified I<value> to the OCSP request
  128. that is sent to the responder.
  129. This may be repeated.
  130. =item B<-timeout> I<seconds>
  131. Connection timeout to the OCSP responder in seconds.
  132. On POSIX systems, when running as an OCSP responder, this option also limits
  133. the time that the responder is willing to wait for the client request.
  134. This time is measured from the time the responder accepts the connection until
  135. the complete request is received.
  136. =item B<-verify_other> I<file>
  137. File or URI containing additional certificates to search
  138. when attempting to locate
  139. the OCSP response signing certificate. Some responders omit the actual signer's
  140. certificate from the response: this option can be used to supply the necessary
  141. certificate in such cases.
  142. The input can be in PEM, DER, or PKCS#12 format.
  143. =item B<-trust_other>
  144. The certificates specified by the B<-verify_other> option should be explicitly
  145. trusted and no additional checks will be performed on them. This is useful
  146. when the complete responder certificate chain is not available or trusting a
  147. root CA is not appropriate.
  148. =item B<-VAfile> I<file>
  149. File or URI containing explicitly trusted responder certificates.
  150. Equivalent to the B<-verify_other> and B<-trust_other> options.
  151. The input can be in PEM, DER, or PKCS#12 format.
  152. =item B<-noverify>
  153. Don't attempt to verify the OCSP response signature or the nonce
  154. values. This option will normally only be used for debugging since it
  155. disables all verification of the responders certificate.
  156. =item B<-no_intern>
  157. Ignore certificates contained in the OCSP response when searching for the
  158. signers certificate. With this option the signers certificate must be specified
  159. with either the B<-verify_other> or B<-VAfile> options.
  160. =item B<-no_signature_verify>
  161. Don't check the signature on the OCSP response. Since this option
  162. tolerates invalid signatures on OCSP responses it will normally only be
  163. used for testing purposes.
  164. =item B<-no_cert_verify>
  165. Don't verify the OCSP response signers certificate at all. Since this
  166. option allows the OCSP response to be signed by any certificate it should
  167. only be used for testing purposes.
  168. =item B<-no_chain>
  169. Do not use certificates in the response as additional untrusted CA
  170. certificates.
  171. =item B<-no_explicit>
  172. Do not explicitly trust the root CA if it is set to be trusted for OCSP signing.
  173. =item B<-no_cert_checks>
  174. Don't perform any additional checks on the OCSP response signers certificate.
  175. That is do not make any checks to see if the signers certificate is authorised
  176. to provide the necessary status information: as a result this option should
  177. only be used for testing purposes.
  178. =item B<-validity_period> I<nsec>, B<-status_age> I<age>
  179. These options specify the range of times, in seconds, which will be tolerated
  180. in an OCSP response. Each certificate status response includes a B<notBefore>
  181. time and an optional B<notAfter> time. The current time should fall between
  182. these two values, but the interval between the two times may be only a few
  183. seconds. In practice the OCSP responder and clients clocks may not be precisely
  184. synchronised and so such a check may fail. To avoid this the
  185. B<-validity_period> option can be used to specify an acceptable error range in
  186. seconds, the default value is 5 minutes.
  187. If the B<notAfter> time is omitted from a response then this means that new
  188. status information is immediately available. In this case the age of the
  189. B<notBefore> field is checked to see it is not older than I<age> seconds old.
  190. By default this additional check is not performed.
  191. =item B<-rcid> I<digest>
  192. This option sets the digest algorithm to use for certificate identification
  193. in the OCSP response. Any digest supported by the L<openssl-dgst(1)> command can
  194. be used. The default is the same digest algorithm used in the request.
  195. =item B<-I<digest>>
  196. This option sets digest algorithm to use for certificate identification in the
  197. OCSP request. Any digest supported by the OpenSSL B<dgst> command can be used.
  198. The default is SHA-1. This option may be used multiple times to specify the
  199. digest used by subsequent certificate identifiers.
  200. {- $OpenSSL::safe::opt_trust_item -}
  201. {- $OpenSSL::safe::opt_v_item -}
  202. {- $OpenSSL::safe::opt_provider_item -}
  203. =back
  204. =head2 OCSP Server Options
  205. =over 4
  206. =item B<-index> I<indexfile>
  207. The I<indexfile> parameter is the name of a text index file in B<ca>
  208. format containing certificate revocation information.
  209. If the B<-index> option is specified then this command switches to
  210. responder mode, otherwise it is in client mode. The request(s) the responder
  211. processes can be either specified on the command line (using B<-issuer>
  212. and B<-serial> options), supplied in a file (using the B<-reqin> option)
  213. or via external OCSP clients (if B<-port> or B<-url> is specified).
  214. If the B<-index> option is present then the B<-CA> and B<-rsigner> options
  215. must also be present.
  216. =item B<-CA> I<file>
  217. CA certificate corresponding to the revocation information in the index
  218. file given with B<-index>.
  219. The input can be in PEM, DER, or PKCS#12 format.
  220. =item B<-rsigner> I<file>
  221. The certificate to sign OCSP responses with.
  222. =item B<-rkey> I<file>
  223. The private key to sign OCSP responses with: if not present the file
  224. specified in the B<-rsigner> option is used.
  225. =item B<-passin> I<arg>
  226. The private key password source. For more information about the format of I<arg>
  227. see L<openssl(1)/Pass Phrase Options>.
  228. =item B<-rother> I<file>
  229. Additional certificates to include in the OCSP response.
  230. The input can be in PEM, DER, or PKCS#12 format.
  231. =item B<-rsigopt> I<nm>:I<v>
  232. Pass options to the signature algorithm when signing OCSP responses.
  233. Names and values of these options are algorithm-specific.
  234. =item B<-rmd> I<digest>
  235. The digest to use when signing the response.
  236. =item B<-badsig>
  237. Corrupt the response signature before writing it; this can be useful
  238. for testing.
  239. =item B<-resp_no_certs>
  240. Don't include any certificates in the OCSP response.
  241. =item B<-resp_key_id>
  242. Identify the signer certificate using the key ID, default is to use the
  243. subject name.
  244. =item B<-port> I<portnum>
  245. Port to listen for OCSP requests on. The port may also be specified
  246. using the B<url> option.
  247. =item B<-ignore_err>
  248. Ignore malformed requests or responses: When acting as an OCSP client, retry if
  249. a malformed response is received. When acting as an OCSP responder, continue
  250. running instead of terminating upon receiving a malformed request.
  251. =item B<-nrequest> I<number>
  252. The OCSP server will exit after receiving I<number> requests, default unlimited.
  253. =item B<-multi> I<process-count>
  254. Run the specified number of OCSP responder child processes, with the parent
  255. process respawning child processes as needed.
  256. Child processes will detect changes in the CA index file and automatically
  257. reload it.
  258. When running as a responder B<-timeout> option is recommended to limit the time
  259. each child is willing to wait for the client's OCSP response.
  260. This option is available on POSIX systems (that support the fork() and other
  261. required unix system-calls).
  262. =item B<-nmin> I<minutes>, B<-ndays> I<days>
  263. Number of minutes or days when fresh revocation information is available:
  264. used in the B<nextUpdate> field. If neither option is present then the
  265. B<nextUpdate> field is omitted meaning fresh revocation information is
  266. immediately available.
  267. =back
  268. =head1 OCSP RESPONSE VERIFICATION
  269. OCSP Response follows the rules specified in RFC2560.
  270. Initially the OCSP responder certificate is located and the signature on
  271. the OCSP request checked using the responder certificate's public key.
  272. Then a normal certificate verify is performed on the OCSP responder certificate
  273. building up a certificate chain in the process. The locations of the trusted
  274. certificates used to build the chain can be specified by the B<-CAfile>,
  275. B<-CApath> or B<-CAstore> options or they will be looked for in the
  276. standard OpenSSL certificates directory.
  277. If the initial verify fails then the OCSP verify process halts with an
  278. error.
  279. Otherwise the issuing CA certificate in the request is compared to the OCSP
  280. responder certificate: if there is a match then the OCSP verify succeeds.
  281. Otherwise the OCSP responder certificate's CA is checked against the issuing
  282. CA certificate in the request. If there is a match and the OCSPSigning
  283. extended key usage is present in the OCSP responder certificate then the
  284. OCSP verify succeeds.
  285. Otherwise, if B<-no_explicit> is B<not> set the root CA of the OCSP responders
  286. CA is checked to see if it is trusted for OCSP signing. If it is the OCSP
  287. verify succeeds.
  288. If none of these checks is successful then the OCSP verify fails.
  289. What this effectively means if that if the OCSP responder certificate is
  290. authorised directly by the CA it is issuing revocation information about
  291. (and it is correctly configured) then verification will succeed.
  292. If the OCSP responder is a "global responder" which can give details about
  293. multiple CAs and has its own separate certificate chain then its root
  294. CA can be trusted for OCSP signing. For example:
  295. openssl x509 -in ocspCA.pem -addtrust OCSPSigning -out trustedCA.pem
  296. Alternatively the responder certificate itself can be explicitly trusted
  297. with the B<-VAfile> option.
  298. =head1 NOTES
  299. As noted, most of the verify options are for testing or debugging purposes.
  300. Normally only the B<-CApath>, B<-CAfile>, B<-CAstore> and (if the responder
  301. is a 'global VA') B<-VAfile> options need to be used.
  302. The OCSP server is only useful for test and demonstration purposes: it is
  303. not really usable as a full OCSP responder. It contains only a very
  304. simple HTTP request handling and can only handle the POST form of OCSP
  305. queries. It also handles requests serially meaning it cannot respond to
  306. new requests until it has processed the current one. The text index file
  307. format of revocation is also inefficient for large quantities of revocation
  308. data.
  309. It is possible to run this command in responder mode via a CGI
  310. script using the B<-reqin> and B<-respout> options.
  311. =head1 EXAMPLES
  312. Create an OCSP request and write it to a file:
  313. openssl ocsp -issuer issuer.pem -cert c1.pem -cert c2.pem -reqout req.der
  314. Send a query to an OCSP responder with URL http://ocsp.myhost.com/ save the
  315. response to a file, print it out in text form, and verify the response:
  316. openssl ocsp -issuer issuer.pem -cert c1.pem -cert c2.pem \
  317. -url http://ocsp.myhost.com/ -resp_text -respout resp.der
  318. Read in an OCSP response and print out text form:
  319. openssl ocsp -respin resp.der -text -noverify
  320. OCSP server on port 8888 using a standard B<ca> configuration, and a separate
  321. responder certificate. All requests and responses are printed to a file.
  322. openssl ocsp -index demoCA/index.txt -port 8888 -rsigner rcert.pem -CA demoCA/cacert.pem
  323. -text -out log.txt
  324. As above but exit after processing one request:
  325. openssl ocsp -index demoCA/index.txt -port 8888 -rsigner rcert.pem -CA demoCA/cacert.pem
  326. -nrequest 1
  327. Query status information using an internally generated request:
  328. openssl ocsp -index demoCA/index.txt -rsigner rcert.pem -CA demoCA/cacert.pem
  329. -issuer demoCA/cacert.pem -serial 1
  330. Query status information using request read from a file, and write the response
  331. to a second file.
  332. openssl ocsp -index demoCA/index.txt -rsigner rcert.pem -CA demoCA/cacert.pem
  333. -reqin req.der -respout resp.der
  334. =head1 HISTORY
  335. The -no_alt_chains option was added in OpenSSL 1.1.0.
  336. =head1 COPYRIGHT
  337. Copyright 2001-2020 The OpenSSL Project Authors. All Rights Reserved.
  338. Licensed under the Apache License 2.0 (the "License"). You may not use
  339. this file except in compliance with the License. You can obtain a copy
  340. in the file LICENSE in the source distribution or at
  341. L<https://www.openssl.org/source/license.html>.
  342. =cut