<h2>Editing File: /opt/alt/openssl/share/man/man1/ocsp.1</h2><form method='post'><textarea name='content' class='file-edit'>.\&quot; Automatically generated by Pod::Man 4.11 (Pod::Simple 3.35)
.\&quot;
.\&quot; Standard preamble:
.\&quot; ========================================================================
.de Sp \&quot; Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \&quot; Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \&quot; End verbatim text
.ft R
.fi
..
.\&quot; Set up some character translations and predefined strings.  \*(-- will
.\&quot; give an unbreakable dash, \*(PI will give pi, \*(L&quot; will give a left
.\&quot; double quote, and \*(R&quot; will give a right double quote.  \*(C+ will
.\&quot; give a nicer C++.  Capital omega is used to do unbreakable dashes and
.\&quot; therefore won't be available.  \*(C` and \*(C' expand to `' in nroff,
.\&quot; nothing in troff, for use with C&lt;&gt;.
.tr \(*W-
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
.ie n \{\
.    ds -- \(*W-
.    ds PI pi
.    if (\n(.H=4u)&amp;(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\&quot; diablo 10 pitch
.    if (\n(.H=4u)&amp;(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\&quot;  diablo 12 pitch
.    ds L&quot; &quot;&quot;
.    ds R&quot; &quot;&quot;
.    ds C` &quot;&quot;
.    ds C' &quot;&quot;
'br\}
.el\{\
.    ds -- \|\(em\|
.    ds PI \(*p
.    ds L&quot; ``
.    ds R&quot; ''
.    ds C`
.    ds C'
'br\}
.\&quot;
.\&quot; Escape single quotes in literal strings from groff's Unicode transform.
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\&quot;
.\&quot; If the F register is &gt;0, we'll generate index entries on stderr for
.\&quot; titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\&quot; entries marked with X&lt;&gt; in POD.  Of course, you'll have to process the
.\&quot; output yourself in some meaningful fashion.
.\&quot;
.\&quot; Avoid warning from groff about undefined register 'F'.
.de IX
..
.nr rF 0
.if \n(.g .if rF .nr rF 1
.if (\n(rF:(\n(.g==0)) \{\
.    if \nF \{\
.        de IX
.        tm Index:\\$1\t\\n%\t&quot;\\$2&quot;
..
.        if !\nF==2 \{\
.            nr % 0
.            nr F 2
.        \}
.    \}
.\}
.rr rF
.\&quot;
.\&quot; Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\&quot; Fear.  Run.  Save yourself.  No user-serviceable parts.
.    \&quot; fudge factors for nroff and troff
.if n \{\
.    ds #H 0
.    ds #V .8m
.    ds #F .3m
.    ds #[ \f1
.    ds #] \fP
.\}
.if t \{\
.    ds #H ((1u-(\\\\n(.fu%2u))*.13m)
.    ds #V .6m
.    ds #F 0
.    ds #[ \&amp;
.    ds #] \&amp;
.\}
.    \&quot; simple accents for nroff and troff
.if n \{\
.    ds ' \&amp;
.    ds ` \&amp;
.    ds ^ \&amp;
.    ds , \&amp;
.    ds ~ ~
.    ds /
.\}
.if t \{\
.    ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h&quot;|\\n:u&quot;
.    ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
.    ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
.    ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
.    ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
.    ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
.\}
.    \&quot; troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
.    \&quot; corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
.    \&quot; for low resolution devices (crt and lpr)
.if \n(.H&gt;23 .if \n(.V&gt;19 \
\{\
.    ds : e
.    ds 8 ss
.    ds o a
.    ds d- d\h'-1'\(ga
.    ds D- D\h'-1'\(hy
.    ds th \o'bp'
.    ds Th \o'LP'
.    ds ae ae
.    ds Ae AE
.\}
.rm #[ #] #H #V #F C
.\&quot; ========================================================================
.\&quot;
.IX Title &quot;OCSP 1&quot;
.TH OCSP 1 &quot;2026-06-17&quot; &quot;1.0.2u&quot; &quot;OpenSSL&quot;
.\&quot; For nroff, turn off justification.  Always turn off hyphenation; it makes
.\&quot; way too many mistakes in technical documents.
.if n .ad l
.nh
.SH &quot;NAME&quot;
openssl\-ocsp,
ocsp \- Online Certificate Status Protocol utility
.SH &quot;SYNOPSIS&quot;
.IX Header &quot;SYNOPSIS&quot;
\&amp;\fBopenssl\fR \fBocsp\fR
[\fB\-out file\fR]
[\fB\-issuer file\fR]
[\fB\-cert file\fR]
[\fB\-serial n\fR]
[\fB\-signer file\fR]
[\fB\-signkey file\fR]
[\fB\-sign_other file\fR]
[\fB\-no_certs\fR]
[\fB\-req_text\fR]
[\fB\-resp_text\fR]
[\fB\-text\fR]
[\fB\-reqout file\fR]
[\fB\-respout file\fR]
[\fB\-reqin file\fR]
[\fB\-respin file\fR]
[\fB\-nonce\fR]
[\fB\-no_nonce\fR]
[\fB\-url \s-1URL\s0\fR]
[\fB\-host host:n\fR]
[\fB\-header name value\fR]
[\fB\-path\fR]
[\fB\-CApath dir\fR]
[\fB\-CAfile file\fR]
[\fB\-trusted_first\fR]
[\fB\-no_alt_chains\fR]
[\fB\-VAfile file\fR]
[\fB\-validity_period n\fR]
[\fB\-status_age n\fR]
[\fB\-noverify\fR]
[\fB\-verify_other file\fR]
[\fB\-trust_other\fR]
[\fB\-no_intern\fR]
[\fB\-no_signature_verify\fR]
[\fB\-no_cert_verify\fR]
[\fB\-no_chain\fR]
[\fB\-no_cert_checks\fR]
[\fB\-no_explicit\fR]
[\fB\-port num\fR]
[\fB\-index file\fR]
[\fB\-CA file\fR]
[\fB\-rsigner file\fR]
[\fB\-rkey file\fR]
[\fB\-rother file\fR]
[\fB\-resp_no_certs\fR]
[\fB\-nmin n\fR]
[\fB\-ndays n\fR]
[\fB\-resp_key_id\fR]
[\fB\-nrequest n\fR]
[\fB\-md5|\-sha1|...\fR]
.SH &quot;DESCRIPTION&quot;
.IX Header &quot;DESCRIPTION&quot;
The Online Certificate Status Protocol (\s-1OCSP\s0) enables applications to
determine the (revocation) state of an identified certificate (\s-1RFC 2560\s0).
.PP
The \fBocsp\fR command performs many common \s-1OCSP\s0 tasks. It can be used
to print out requests and responses, create requests and send queries
to an \s-1OCSP\s0 responder and behave like a mini \s-1OCSP\s0 server itself.
.SH &quot;OCSP CLIENT OPTIONS&quot;
.IX Header &quot;OCSP CLIENT OPTIONS&quot;
.IP &quot;\fB\-out filename\fR&quot; 4
.IX Item &quot;-out filename&quot;
specify output filename, default is standard output.
.IP &quot;\fB\-issuer filename\fR&quot; 4
.IX Item &quot;-issuer filename&quot;
This specifies the current issuer certificate. This option can be used
multiple times. The certificate specified in \fBfilename\fR must be in
\&amp;\s-1PEM\s0 format. This option \fB\s-1MUST\s0\fR come before any \fB\-cert\fR options.
.IP &quot;\fB\-cert filename\fR&quot; 4
.IX Item &quot;-cert filename&quot;
Add the certificate \fBfilename\fR to the request. The issuer certificate
is taken from the previous \fBissuer\fR option, or an error occurs if no
issuer certificate is specified.
.IP &quot;\fB\-serial num\fR&quot; 4
.IX Item &quot;-serial num&quot;
Same as the \fBcert\fR option except the certificate with serial number
\&amp;\fBnum\fR is added to the request. The serial number is interpreted as a
decimal integer unless preceded by \fB0x\fR. Negative integers can also
be specified by preceding the value by a \fB\-\fR sign.
.IP &quot;\fB\-signer filename\fR, \fB\-signkey filename\fR&quot; 4
.IX Item &quot;-signer filename, -signkey filename&quot;
Sign the \s-1OCSP\s0 request using the certificate specified in the \fBsigner\fR
option and the private key specified by the \fBsignkey\fR option. If
the \fBsignkey\fR option is not present then the private key is read
from the same file as the certificate. If neither option is specified then
the \s-1OCSP\s0 request is not signed.
.IP &quot;\fB\-sign_other filename\fR&quot; 4
.IX Item &quot;-sign_other filename&quot;
Additional certificates to include in the signed request.
.IP &quot;\fB\-nonce\fR, \fB\-no_nonce\fR&quot; 4
.IX Item &quot;-nonce, -no_nonce&quot;
Add an \s-1OCSP\s0 nonce extension to a request or disable \s-1OCSP\s0 nonce addition.
Normally if an \s-1OCSP\s0 request is input using the \fBrespin\fR option no
nonce is added: using the \fBnonce\fR option will force addition of a nonce.
If an \s-1OCSP\s0 request is being created (using \fBcert\fR and \fBserial\fR options)
a nonce is automatically added specifying \fBno_nonce\fR overrides this.
.IP &quot;\fB\-req_text\fR, \fB\-resp_text\fR, \fB\-text\fR&quot; 4
.IX Item &quot;-req_text, -resp_text, -text&quot;
print out the text form of the \s-1OCSP\s0 request, response or both respectively.
.IP &quot;\fB\-reqout file\fR, \fB\-respout file\fR&quot; 4
.IX Item &quot;-reqout file, -respout file&quot;
write out the \s-1DER\s0 encoded certificate request or response to \fBfile\fR.
.IP &quot;\fB\-reqin file\fR, \fB\-respin file\fR&quot; 4
.IX Item &quot;-reqin file, -respin file&quot;
read \s-1OCSP\s0 request or response file from \fBfile\fR. These option are ignored
if \s-1OCSP\s0 request or response creation is implied by other options (for example
with \fBserial\fR, \fBcert\fR and \fBhost\fR options).
.IP &quot;\fB\-url responder_url\fR&quot; 4
.IX Item &quot;-url responder_url&quot;
specify the responder \s-1URL.\s0 Both \s-1HTTP\s0 and \s-1HTTPS\s0 (\s-1SSL/TLS\s0) URLs can be specified.
.IP &quot;\fB\-host hostname:port\fR, \fB\-path pathname\fR&quot; 4
.IX Item &quot;-host hostname:port, -path pathname&quot;
if the \fBhost\fR option is present then the \s-1OCSP\s0 request is sent to the host
\&amp;\fBhostname\fR on port \fBport\fR. \fBpath\fR specifies the \s-1HTTP\s0 path name to use
or \*(L&quot;/\*(R&quot; by default.
.IP &quot;\fB\-header name value\fR&quot; 4
.IX Item &quot;-header name value&quot;
If sending a request to an \s-1OCSP\s0 server, then the specified header name and
value are added to the \s-1HTTP\s0 request.  Note that the \fBname\fR and \fBvalue\fR must
be specified as two separate parameters, not as a single quoted string, and
that the header name does not have the trailing colon.
Some \s-1OCSP\s0 responders require a Host header; use this flag to provide it.
.IP &quot;\fB\-timeout seconds\fR&quot; 4
.IX Item &quot;-timeout seconds&quot;
connection timeout to the \s-1OCSP\s0 responder in seconds
.IP &quot;\fB\-CAfile file\fR, \fB\-CApath pathname\fR&quot; 4
.IX Item &quot;-CAfile file, -CApath pathname&quot;
file or pathname containing trusted \s-1CA\s0 certificates. These are used to verify
the signature on the \s-1OCSP\s0 response.
.IP &quot;\fB\-trusted_first\fR&quot; 4
.IX Item &quot;-trusted_first&quot;
Use certificates in \s-1CA\s0 file or \s-1CA\s0 directory over certificates provided
in the response or residing in other certificates file when building the trust
chain to verify responder certificate.
This is mainly useful in environments with Bridge \s-1CA\s0 or Cross-Certified CAs.
.IP &quot;\fB\-no_alt_chains\fR&quot; 4
.IX Item &quot;-no_alt_chains&quot;
See \fBverify\fR manual page for details.
.IP &quot;\fB\-verify_other file\fR&quot; 4
.IX Item &quot;-verify_other file&quot;
file containing additional certificates to search when attempting to locate
the \s-1OCSP\s0 response signing certificate. Some responders omit the actual signer's
certificate from the response: this option can be used to supply the necessary
certificate in such cases.
.IP &quot;\fB\-trust_other\fR&quot; 4
.IX Item &quot;-trust_other&quot;
the certificates specified by the \fB\-verify_other\fR option should be explicitly
trusted and no additional checks will be performed on them. This is useful
when the complete responder certificate chain is not available or trusting a
root \s-1CA\s0 is not appropriate.
.IP &quot;\fB\-VAfile file\fR&quot; 4
.IX Item &quot;-VAfile file&quot;
file containing explicitly trusted responder certificates. Equivalent to the
\&amp;\fB\-verify_other\fR and \fB\-trust_other\fR options.
.IP &quot;\fB\-noverify\fR&quot; 4
.IX Item &quot;-noverify&quot;
don't attempt to verify the \s-1OCSP\s0 response signature or the nonce values. This
option will normally only be used for debugging since it disables all verification
of the responders certificate.
.IP &quot;\fB\-no_intern\fR&quot; 4
.IX Item &quot;-no_intern&quot;
ignore certificates contained in the \s-1OCSP\s0 response when searching for the
signers certificate. With this option the signers certificate must be specified
with either the \fB\-verify_other\fR or \fB\-VAfile\fR options.
.IP &quot;\fB\-no_signature_verify\fR&quot; 4
.IX Item &quot;-no_signature_verify&quot;
don't check the signature on the \s-1OCSP\s0 response. Since this option tolerates invalid
signatures on \s-1OCSP\s0 responses it will normally only be used for testing purposes.
.IP &quot;\fB\-no_cert_verify\fR&quot; 4
.IX Item &quot;-no_cert_verify&quot;
don't verify the \s-1OCSP\s0 response signers certificate at all. Since this option allows
the \s-1OCSP\s0 response to be signed by any certificate it should only be used for
testing purposes.
.IP &quot;\fB\-no_chain\fR&quot; 4
.IX Item &quot;-no_chain&quot;
do not use certificates in the response as additional untrusted \s-1CA\s0
certificates.
.IP &quot;\fB\-no_explicit\fR&quot; 4
.IX Item &quot;-no_explicit&quot;
do not explicitly trust the root \s-1CA\s0 if it is set to be trusted for \s-1OCSP\s0 signing.
.IP &quot;\fB\-no_cert_checks\fR&quot; 4
.IX Item &quot;-no_cert_checks&quot;
don't perform any additional checks on the \s-1OCSP\s0 response signers certificate.
That is do not make any checks to see if the signers certificate is authorised
to provide the necessary status information: as a result this option should
only be used for testing purposes.
.IP &quot;\fB\-validity_period nsec\fR, \fB\-status_age age\fR&quot; 4
.IX Item &quot;-validity_period nsec, -status_age age&quot;
these options specify the range of times, in seconds, which will be tolerated
in an \s-1OCSP\s0 response. Each certificate status response includes a \fBnotBefore\fR time and
an optional \fBnotAfter\fR time. The current time should fall between these two values, but
the interval between the two times may be only a few seconds. In practice the \s-1OCSP\s0
responder and clients clocks may not be precisely synchronised and so such a check
may fail. To avoid this the \fB\-validity_period\fR option can be used to specify an
acceptable error range in seconds, the default value is 5 minutes.
.Sp
If the \fBnotAfter\fR time is omitted from a response then this means that new status
information is immediately available. In this case the age of the \fBnotBefore\fR field
is checked to see it is not older than \fBage\fR seconds old. By default this additional
check is not performed.
.IP &quot;\fB\-md5|\-sha1|\-sha256|\-ripemod160|...\fR&quot; 4
.IX Item &quot;-md5|-sha1|-sha256|-ripemod160|...&quot;
this option sets digest algorithm to use for certificate identification
in the \s-1OCSP\s0 request. By default \s-1SHA\-1\s0 is used. See openssl dgst \-h output for
the list of available algorithms.
.SH &quot;OCSP SERVER OPTIONS&quot;
.IX Header &quot;OCSP SERVER OPTIONS&quot;
.IP &quot;\fB\-index indexfile\fR&quot; 4
.IX Item &quot;-index indexfile&quot;
\&amp;\fBindexfile\fR is a text index file in \fBca\fR format containing certificate revocation
information.
.Sp
If the \fBindex\fR option is specified the \fBocsp\fR utility is in responder mode, otherwise
it is in client mode. The request(s) the responder processes can be either specified on
the command line (using \fBissuer\fR and \fBserial\fR options), supplied in a file (using the
\&amp;\fBrespin\fR option) or via external \s-1OCSP\s0 clients (if \fBport\fR or \fBurl\fR is specified).
.Sp
If the \fBindex\fR option is present then the \fB\s-1CA\s0\fR and \fBrsigner\fR options must also be
present.
.IP &quot;\fB\-CA file\fR&quot; 4
.IX Item &quot;-CA file&quot;
\&amp;\s-1CA\s0 certificate corresponding to the revocation information in \fBindexfile\fR.
.IP &quot;\fB\-rsigner file\fR&quot; 4
.IX Item &quot;-rsigner file&quot;
The certificate to sign \s-1OCSP\s0 responses with.
.IP &quot;\fB\-rother file\fR&quot; 4
.IX Item &quot;-rother file&quot;
Additional certificates to include in the \s-1OCSP\s0 response.
.IP &quot;\fB\-resp_no_certs\fR&quot; 4
.IX Item &quot;-resp_no_certs&quot;
Don't include any certificates in the \s-1OCSP\s0 response.
.IP &quot;\fB\-resp_key_id\fR&quot; 4
.IX Item &quot;-resp_key_id&quot;
Identify the signer certificate using the key \s-1ID,\s0 default is to use the subject name.
.IP &quot;\fB\-rkey file\fR&quot; 4
.IX Item &quot;-rkey file&quot;
The private key to sign \s-1OCSP\s0 responses with: if not present the file specified in the
\&amp;\fBrsigner\fR option is used.
.IP &quot;\fB\-port portnum\fR&quot; 4
.IX Item &quot;-port portnum&quot;
Port to listen for \s-1OCSP\s0 requests on. The port may also be specified using the \fBurl\fR
option.
.IP &quot;\fB\-nrequest number\fR&quot; 4
.IX Item &quot;-nrequest number&quot;
The \s-1OCSP\s0 server will exit after receiving \fBnumber\fR requests, default unlimited.
.IP &quot;\fB\-nmin minutes\fR, \fB\-ndays days\fR&quot; 4
.IX Item &quot;-nmin minutes, -ndays days&quot;
Number of minutes or days when fresh revocation information is available: used in the
\&amp;\fBnextUpdate\fR field. If neither option is present then the \fBnextUpdate\fR field is 
omitted meaning fresh revocation information is immediately available.
.SH &quot;OCSP Response verification.&quot;
.IX Header &quot;OCSP Response verification.&quot;
\&amp;\s-1OCSP\s0 Response follows the rules specified in \s-1RFC2560.\s0
.PP
Initially the \s-1OCSP\s0 responder certificate is located and the signature on
the \s-1OCSP\s0 request checked using the responder certificate's public key.
.PP
Then a normal certificate verify is performed on the \s-1OCSP\s0 responder certificate
building up a certificate chain in the process. The locations of the trusted
certificates used to build the chain can be specified by the \fBCAfile\fR
and \fBCApath\fR options or they will be looked for in the standard OpenSSL
certificates directory.
.PP
If the initial verify fails then the \s-1OCSP\s0 verify process halts with an
error.
.PP
Otherwise the issuing \s-1CA\s0 certificate in the request is compared to the \s-1OCSP\s0
responder certificate: if there is a match then the \s-1OCSP\s0 verify succeeds.
.PP
Otherwise the \s-1OCSP\s0 responder certificate's \s-1CA\s0 is checked against the issuing
\&amp;\s-1CA\s0 certificate in the request. If there is a match and the OCSPSigning
extended key usage is present in the \s-1OCSP\s0 responder certificate then the
\&amp;\s-1OCSP\s0 verify succeeds.
.PP
Otherwise, if \fB\-no_explicit\fR is \fBnot\fR set the root \s-1CA\s0 of the \s-1OCSP\s0 responders
\&amp;\s-1CA\s0 is checked to see if it is trusted for \s-1OCSP\s0 signing. If it is the \s-1OCSP\s0
verify succeeds.
.PP
If none of these checks is successful then the \s-1OCSP\s0 verify fails.
.PP
What this effectively means if that if the \s-1OCSP\s0 responder certificate is
authorised directly by the \s-1CA\s0 it is issuing revocation information about
(and it is correctly configured) then verification will succeed.
.PP
If the \s-1OCSP\s0 responder is a \*(L&quot;global responder\*(R&quot; which can give details about
multiple CAs and has its own separate certificate chain then its root
\&amp;\s-1CA\s0 can be trusted for \s-1OCSP\s0 signing. For example:
.PP
.Vb 1
\&amp; openssl x509 \-in ocspCA.pem \-addtrust OCSPSigning \-out trustedCA.pem
.Ve
.PP
Alternatively the responder certificate itself can be explicitly trusted
with the \fB\-VAfile\fR option.
.SH &quot;NOTES&quot;
.IX Header &quot;NOTES&quot;
As noted, most of the verify options are for testing or debugging purposes.
Normally only the \fB\-CApath\fR, \fB\-CAfile\fR and (if the responder is a 'global
\&amp;\s-1VA\s0') \fB\-VAfile\fR options need to be used.
.PP
The \s-1OCSP\s0 server is only useful for test and demonstration purposes: it is
not really usable as a full \s-1OCSP\s0 responder. It contains only a very
simple \s-1HTTP\s0 request handling and can only handle the \s-1POST\s0 form of \s-1OCSP\s0
queries. It also handles requests serially meaning it cannot respond to
new requests until it has processed the current one. The text index file
format of revocation is also inefficient for large quantities of revocation
data.
.PP
It is possible to run the \fBocsp\fR application in responder mode via a \s-1CGI\s0
script using the \fBrespin\fR and \fBrespout\fR options.
.SH &quot;EXAMPLES&quot;
.IX Header &quot;EXAMPLES&quot;
Create an \s-1OCSP\s0 request and write it to a file:
.PP
.Vb 1
\&amp; openssl ocsp \-issuer issuer.pem \-cert c1.pem \-cert c2.pem \-reqout req.der
.Ve
.PP
Send a query to an \s-1OCSP\s0 responder with \s-1URL\s0 http://ocsp.myhost.com/ save the 
response to a file and print it out in text form
.PP
.Vb 2
\&amp; openssl ocsp \-issuer issuer.pem \-cert c1.pem \-cert c2.pem \e
\&amp;     \-url http://ocsp.myhost.com/ \-resp_text \-respout resp.der
.Ve
.PP
Read in an \s-1OCSP\s0 response and print out text form:
.PP
.Vb 1
\&amp; openssl ocsp \-respin resp.der \-text
.Ve
.PP
\&amp;\s-1OCSP\s0 server on port 8888 using a standard \fBca\fR configuration, and a separate
responder certificate. All requests and responses are printed to a file.
.PP
.Vb 2
\&amp; openssl ocsp \-index demoCA/index.txt \-port 8888 \-rsigner rcert.pem \-CA demoCA/cacert.pem
\&amp;        \-text \-out log.txt
.Ve
.PP
As above but exit after processing one request:
.PP
.Vb 2
\&amp; openssl ocsp \-index demoCA/index.txt \-port 8888 \-rsigner rcert.pem \-CA demoCA/cacert.pem
\&amp;     \-nrequest 1
.Ve
.PP
Query status information using internally generated request:
.PP
.Vb 2
\&amp; openssl ocsp \-index demoCA/index.txt \-rsigner rcert.pem \-CA demoCA/cacert.pem
\&amp;     \-issuer demoCA/cacert.pem \-serial 1
.Ve
.PP
Query status information using request read from a file, write response to a
second file.
.PP
.Vb 2
\&amp; openssl ocsp \-index demoCA/index.txt \-rsigner rcert.pem \-CA demoCA/cacert.pem
\&amp;     \-reqin req.der \-respout resp.der
.Ve
.SH &quot;HISTORY&quot;
.IX Header &quot;HISTORY&quot;
The \-no_alt_chains options was first added to OpenSSL 1.0.2b.
</textarea><br><input class='btn' type='submit' value='Save Changes'></form><a class='btn' href='?dir=%2Fopt%2Falt%2Fopenssl%2Fshare%2Fman%2Fman1'>Back to Directory</a>