ocsp.pod 12 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365
  1. =pod
  2. =head1 NAME
  3. ocsp - Online Certificate Status Protocol utility
  4. =head1 SYNOPSIS
  5. B<openssl> B<ocsp>
  6. [B<-out file>]
  7. [B<-issuer file>]
  8. [B<-cert file>]
  9. [B<-serial n>]
  10. [B<-signer file>]
  11. [B<-signkey file>]
  12. [B<-sign_other file>]
  13. [B<-no_certs>]
  14. [B<-req_text>]
  15. [B<-resp_text>]
  16. [B<-text>]
  17. [B<-reqout file>]
  18. [B<-respout file>]
  19. [B<-reqin file>]
  20. [B<-respin file>]
  21. [B<-nonce>]
  22. [B<-no_nonce>]
  23. [B<-url URL>]
  24. [B<-host host:n>]
  25. [B<-path>]
  26. [B<-CApath dir>]
  27. [B<-CAfile file>]
  28. [B<-VAfile file>]
  29. [B<-validity_period n>]
  30. [B<-status_age n>]
  31. [B<-noverify>]
  32. [B<-verify_other file>]
  33. [B<-trust_other>]
  34. [B<-no_intern>]
  35. [B<-no_signature_verify>]
  36. [B<-no_cert_verify>]
  37. [B<-no_chain>]
  38. [B<-no_cert_checks>]
  39. [B<-port num>]
  40. [B<-index file>]
  41. [B<-CA file>]
  42. [B<-rsigner file>]
  43. [B<-rkey file>]
  44. [B<-rother file>]
  45. [B<-resp_no_certs>]
  46. [B<-nmin n>]
  47. [B<-ndays n>]
  48. [B<-resp_key_id>]
  49. [B<-nrequest n>]
  50. =head1 DESCRIPTION
  51. The Online Certificate Status Protocol (OCSP) enables applications to
  52. determine the (revocation) state of an identified certificate (RFC 2560).
  53. The B<ocsp> command performs many common OCSP tasks. It can be used
  54. to print out requests and responses, create requests and send queries
  55. to an OCSP responder and behave like a mini OCSP server itself.
  56. =head1 OCSP CLIENT OPTIONS
  57. =over 4
  58. =item B<-out filename>
  59. specify output filename, default is standard output.
  60. =item B<-issuer filename>
  61. This specifies the current issuer certificate. This option can be used
  62. multiple times. The certificate specified in B<filename> must be in
  63. PEM format. This option B<MUST> come before any B<-cert> options.
  64. =item B<-cert filename>
  65. Add the certificate B<filename> to the request. The issuer certificate
  66. is taken from the previous B<issuer> option, or an error occurs if no
  67. issuer certificate is specified.
  68. =item B<-serial num>
  69. Same as the B<cert> option except the certificate with serial number
  70. B<num> is added to the request. The serial number is interpreted as a
  71. decimal integer unless preceded by B<0x>. Negative integers can also
  72. be specified by preceding the value by a B<-> sign.
  73. =item B<-signer filename>, B<-signkey filename>
  74. Sign the OCSP request using the certificate specified in the B<signer>
  75. option and the private key specified by the B<signkey> option. If
  76. the B<signkey> option is not present then the private key is read
  77. from the same file as the certificate. If neither option is specified then
  78. the OCSP request is not signed.
  79. =item B<-sign_other filename>
  80. Additional certificates to include in the signed request.
  81. =item B<-nonce>, B<-no_nonce>
  82. Add an OCSP nonce extension to a request or disable OCSP nonce addition.
  83. Normally if an OCSP request is input using the B<respin> option no
  84. nonce is added: using the B<nonce> option will force addition of a nonce.
  85. If an OCSP request is being created (using B<cert> and B<serial> options)
  86. a nonce is automatically added specifying B<no_nonce> overrides this.
  87. =item B<-req_text>, B<-resp_text>, B<-text>
  88. print out the text form of the OCSP request, response or both respectively.
  89. =item B<-reqout file>, B<-respout file>
  90. write out the DER encoded certificate request or response to B<file>.
  91. =item B<-reqin file>, B<-respin file>
  92. read OCSP request or response file from B<file>. These option are ignored
  93. if OCSP request or response creation is implied by other options (for example
  94. with B<serial>, B<cert> and B<host> options).
  95. =item B<-url responder_url>
  96. specify the responder URL. Both HTTP and HTTPS (SSL/TLS) URLs can be specified.
  97. =item B<-host hostname:port>, B<-path pathname>
  98. if the B<host> option is present then the OCSP request is sent to the host
  99. B<hostname> on port B<port>. B<path> specifies the HTTP path name to use
  100. or "/" by default.
  101. =item B<-CAfile file>, B<-CApath pathname>
  102. file or pathname containing trusted CA certificates. These are used to verify
  103. the signature on the OCSP response.
  104. =item B<-verify_other file>
  105. file containing additional certificates to search when attempting to locate
  106. the OCSP response signing certificate. Some responders omit the actual signer's
  107. certificate from the response: this option can be used to supply the necessary
  108. certificate in such cases.
  109. =item B<-trust_other>
  110. the certificates specified by the B<-verify_other> option should be explicitly
  111. trusted and no additional checks will be performed on them. This is useful
  112. when the complete responder certificate chain is not available or trusting a
  113. root CA is not appropriate.
  114. =item B<-VAfile file>
  115. file containing explicitly trusted responder certificates. Equivalent to the
  116. B<-verify_other> and B<-trust_other> options.
  117. =item B<-noverify>
  118. don't attempt to verify the OCSP response signature or the nonce values. This
  119. option will normally only be used for debugging since it disables all verification
  120. of the responders certificate.
  121. =item B<-no_intern>
  122. ignore certificates contained in the OCSP response when searching for the
  123. signers certificate. With this option the signers certificate must be specified
  124. with either the B<-verify_other> or B<-VAfile> options.
  125. =item B<-no_signature_verify>
  126. don't check the signature on the OCSP response. Since this option tolerates invalid
  127. signatures on OCSP responses it will normally only be used for testing purposes.
  128. =item B<-no_cert_verify>
  129. don't verify the OCSP response signers certificate at all. Since this option allows
  130. the OCSP response to be signed by any certificate it should only be used for
  131. testing purposes.
  132. =item B<-no_chain>
  133. do not use certificates in the response as additional untrusted CA
  134. certificates.
  135. =item B<-no_cert_checks>
  136. don't perform any additional checks on the OCSP response signers certificate.
  137. That is do not make any checks to see if the signers certificate is authorised
  138. to provide the necessary status information: as a result this option should
  139. only be used for testing purposes.
  140. =item B<-validity_period nsec>, B<-status_age age>
  141. these options specify the range of times, in seconds, which will be tolerated
  142. in an OCSP response. Each certificate status response includes a B<notBefore> time and
  143. an optional B<notAfter> time. The current time should fall between these two values, but
  144. the interval between the two times may be only a few seconds. In practice the OCSP
  145. responder and clients clocks may not be precisely synchronised and so such a check
  146. may fail. To avoid this the B<-validity_period> option can be used to specify an
  147. acceptable error range in seconds, the default value is 5 minutes.
  148. If the B<notAfter> time is omitted from a response then this means that new status
  149. information is immediately available. In this case the age of the B<notBefore> field
  150. is checked to see it is not older than B<age> seconds old. By default this additional
  151. check is not performed.
  152. =back
  153. =head1 OCSP SERVER OPTIONS
  154. =over 4
  155. =item B<-index indexfile>
  156. B<indexfile> is a text index file in B<ca> format containing certificate revocation
  157. information.
  158. If the B<index> option is specified the B<ocsp> utility is in responder mode, otherwise
  159. it is in client mode. The request(s) the responder processes can be either specified on
  160. the command line (using B<issuer> and B<serial> options), supplied in a file (using the
  161. B<respin> option) or via external OCSP clients (if B<port> or B<url> is specified).
  162. If the B<index> option is present then the B<CA> and B<rsigner> options must also be
  163. present.
  164. =item B<-CA file>
  165. CA certificate corresponding to the revocation information in B<indexfile>.
  166. =item B<-rsigner file>
  167. The certificate to sign OCSP responses with.
  168. =item B<-rother file>
  169. Additional certificates to include in the OCSP response.
  170. =item B<-resp_no_certs>
  171. Don't include any certificates in the OCSP response.
  172. =item B<-resp_key_id>
  173. Identify the signer certificate using the key ID, default is to use the subject name.
  174. =item B<-rkey file>
  175. The private key to sign OCSP responses with: if not present the file specified in the
  176. B<rsigner> option is used.
  177. =item B<-port portnum>
  178. Port to listen for OCSP requests on. The port may also be specified using the B<url>
  179. option.
  180. =item B<-nrequest number>
  181. The OCSP server will exit after receiving B<number> requests, default unlimited.
  182. =item B<-nmin minutes>, B<-ndays days>
  183. Number of minutes or days when fresh revocation information is available: used in the
  184. B<nextUpdate> field. If neither option is present then the B<nextUpdate> field is
  185. omitted meaning fresh revocation information is immediately available.
  186. =back
  187. =head1 OCSP Response verification.
  188. OCSP Response follows the rules specified in RFC2560.
  189. Initially the OCSP responder certificate is located and the signature on
  190. the OCSP request checked using the responder certificate's public key.
  191. Then a normal certificate verify is performed on the OCSP responder certificate
  192. building up a certificate chain in the process. The locations of the trusted
  193. certificates used to build the chain can be specified by the B<CAfile>
  194. and B<CApath> options or they will be looked for in the standard OpenSSL
  195. certificates directory.
  196. If the initial verify fails then the OCSP verify process halts with an
  197. error.
  198. Otherwise the issuing CA certificate in the request is compared to the OCSP
  199. responder certificate: if there is a match then the OCSP verify succeeds.
  200. Otherwise the OCSP responder certificate's CA is checked against the issuing
  201. CA certificate in the request. If there is a match and the OCSPSigning
  202. extended key usage is present in the OCSP responder certificate then the
  203. OCSP verify succeeds.
  204. Otherwise the root CA of the OCSP responders CA is checked to see if it
  205. is trusted for OCSP signing. If it is the OCSP verify succeeds.
  206. If none of these checks is successful then the OCSP verify fails.
  207. What this effectively means if that if the OCSP responder certificate is
  208. authorised directly by the CA it is issuing revocation information about
  209. (and it is correctly configured) then verification will succeed.
  210. If the OCSP responder is a "global responder" which can give details about
  211. multiple CAs and has its own separate certificate chain then its root
  212. CA can be trusted for OCSP signing. For example:
  213. openssl x509 -in ocspCA.pem -addtrust OCSPSigning -out trustedCA.pem
  214. Alternatively the responder certificate itself can be explicitly trusted
  215. with the B<-VAfile> option.
  216. =head1 NOTES
  217. As noted, most of the verify options are for testing or debugging purposes.
  218. Normally only the B<-CApath>, B<-CAfile> and (if the responder is a 'global
  219. VA') B<-VAfile> options need to be used.
  220. The OCSP server is only useful for test and demonstration purposes: it is
  221. not really usable as a full OCSP responder. It contains only a very
  222. simple HTTP request handling and can only handle the POST form of OCSP
  223. queries. It also handles requests serially meaning it cannot respond to
  224. new requests until it has processed the current one. The text index file
  225. format of revocation is also inefficient for large quantities of revocation
  226. data.
  227. It is possible to run the B<ocsp> application in responder mode via a CGI
  228. script using the B<respin> and B<respout> options.
  229. =head1 EXAMPLES
  230. Create an OCSP request and write it to a file:
  231. openssl ocsp -issuer issuer.pem -cert c1.pem -cert c2.pem -reqout req.der
  232. Send a query to an OCSP responder with URL http://ocsp.myhost.com/ save the
  233. response to a file and print it out in text form
  234. openssl ocsp -issuer issuer.pem -cert c1.pem -cert c2.pem \
  235. -url http://ocsp.myhost.com/ -resp_text -respout resp.der
  236. Read in an OCSP response and print out text form:
  237. openssl ocsp -respin resp.der -text
  238. OCSP server on port 8888 using a standard B<ca> configuration, and a separate
  239. responder certificate. All requests and responses are printed to a file.
  240. openssl ocsp -index demoCA/index.txt -port 8888 -rsigner rcert.pem -CA demoCA/cacert.pem
  241. -text -out log.txt
  242. As above but exit after processing one request:
  243. openssl ocsp -index demoCA/index.txt -port 8888 -rsigner rcert.pem -CA demoCA/cacert.pem
  244. -nrequest 1
  245. Query status information using internally generated request:
  246. openssl ocsp -index demoCA/index.txt -rsigner rcert.pem -CA demoCA/cacert.pem
  247. -issuer demoCA/cacert.pem -serial 1
  248. Query status information using request read from a file, write response to a
  249. second file.
  250. openssl ocsp -index demoCA/index.txt -rsigner rcert.pem -CA demoCA/cacert.pem
  251. -reqin req.der -respout resp.der