Name Synopsis: Ocsp RFC 2560 Ocsp Ocsp Ocsp
Name Synopsis: Ocsp RFC 2560 Ocsp Ocsp Ocsp
Name Synopsis: Ocsp RFC 2560 Ocsp Ocsp Ocsp
NAME
openssl-ocsp, ocsp - Online Certificate Status Protocol utility
SYNOPSIS
openssl ocsp [-help] [-out file] [-issuer file] [-cert file] [-serial n] [-signer file] [-signkey file]
[-sign_other file] [-no_certs] [-req_text] [-resp_text] [-text] [-reqout file] [-respout file] [-reqin
file] [-respin file] [-nonce] [-no_nonce] [-url URL] [-host host:port] [-multi process-count]
[-header] [-path] [-CApath dir] [-CAfile file] [-no-CAfile] [-no-CApath] [-attime timestamp]
[-check_ss_sig] [-crl_check] [-crl_check_all] [-explicit_policy] [-extended_crl] [-ignore_critical]
[-inhibit_any] [-inhibit_map] [-no_check_time] [-partial_chain] [-policy arg] [-policy_check]
[-policy_print] [-purpose purpose] [-suiteB_128] [-suiteB_128_only] [-suiteB_192] [-trusted_first]
[-no_alt_chains] [-use_deltas] [-auth_level num] [-verify_depth num] [-verify_email email]
[-verify_hostname hostname] [-verify_ip ip] [-verify_name name] [-x509_strict] [-VAfile file]
[-validity_period n] [-status_age n] [-noverify] [-verify_other file] [-trust_other] [-no_intern]
[-no_signature_verify] [-no_cert_verify] [-no_chain] [-no_cert_checks] [-no_explicit] [-port num]
[-ignore_err] [-index file] [-CA file] [-rsigner file] [-rkey file] [-rother file] [-rsigopt nm:v]
[-resp_no_certs] [-nmin n] [-ndays n] [-resp_key_id] [-nrequest n] [-digest]
DESCRIPTION
The Online Certificate Status Protocol (OCSP) enables applications to determine the (revocation) state of an
identified certificate (RFC 2560).
The ocsp command performs many common OCSP tasks. It can be used to print out requests and responses,
create requests and send queries to an OCSP responder and behave like a mini OCSP server itself.
OPTIONS
This command operates as either a client or a server. The options are described below, divided into those
two modes.
OCSP Client Options
-help
Print out a usage message.
-out filename
specify output filename, default is standard output.
-issuer filename
This specifies the current issuer certificate. This option can be used multiple times. The certificate
specified in filename must be in PEM format. This option MUST come before any -cert options.
-cert filename
Add the certificate filename to the request. The issuer certificate is taken from the previous issuer
option, or an error occurs if no issuer certificate is specified.
-serial num
Same as the cert option except the certificate with serial number num is added to the request. The
serial number is interpreted as a decimal integer unless preceded by 0x. Negative integers can also be
specified by preceding the value by a - sign.
-signer filename, -signkey filename
Sign the OCSP request using the certificate specified in the signer option and the private key specified
by the signkey option. If the signkey option is not present then the private key is read from the same
file as the certificate. If neither option is specified then the OCSP request is not signed.
-sign_other filename
Additional certificates to include in the signed request.
-nonce, -no_nonce
Add an OCSP nonce extension to a request or disable OCSP nonce addition. Normally if an OCSP
request is input using the reqin option no nonce is added: using the nonce option will force addition
of a nonce. If an OCSP request is being created (using cert and serial options) a nonce is
automatically added specifying no_nonce overrides this.
1.1.1k 2021-03-25 1
OCSP(1SSL) OpenSSL OCSP(1SSL)
1.1.1k 2021-03-25 2
OCSP(1SSL) OpenSSL OCSP(1SSL)
-VAfile file
File containing explicitly trusted responder certificates. Equivalent to the -verify_other and
-trust_other options.
-noverify
Don’t attempt to verify the OCSP response signature or the nonce values. This option will normally
only be used for debugging since it disables all verification of the responders certificate.
-no_intern
Ignore certificates contained in the OCSP response when searching for the signers certificate. With this
option the signers certificate must be specified with either the -verify_other or -VAfile options.
-no_signature_verify
Don’t check the signature on the OCSP response. Since this option tolerates invalid signatures on OCSP
responses it will normally only be used for testing purposes.
-no_cert_verify
Don’t verify the OCSP response signers certificate at all. Since this option allows the OCSP response to
be signed by any certificate it should only be used for testing purposes.
-no_chain
Do not use certificates in the response as additional untrusted CA certificates.
-no_explicit
Do not explicitly trust the root CA if it is set to be trusted for OCSP signing.
-no_cert_checks
Don’t perform any additional checks on the OCSP 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.
-validity_period nsec, -status_age age
These options specify the range of times, in seconds, which will be tolerated in an OCSP response.
Each certificate status response includes a notBefore time and an optional notAfter 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 OCSP responder and clients clocks may not be precisely synchronised and so
such a check may fail. To avoid this the -validity_period option can be used to specify an acceptable
error range in seconds, the default value is 5 minutes.
If the notAfter time is omitted from a response then this means that new status information is
immediately available. In this case the age of the notBefore field is checked to see it is not older than
age seconds old. By default this additional check is not performed.
-digest
This option sets digest algorithm to use for certificate identification in the OCSP request. Any digest
supported by the OpenSSL dgst command can be used. The default is SHA-1. This option may be
used multiple times to specify the digest used by subsequent certificate identifiers.
OCSP Server Options
-index indexfile
The indexfile parameter is the name of a text index file in ca format containing certificate revocation
information.
If the index option is specified the ocsp 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 issuer and
serial options), supplied in a file (using the reqin option) or via external OCSP clients (if port or url is
specified).
If the index option is present then the CA and rsigner options must also be present.
-CA file
CA certificate corresponding to the revocation information in indexfile.
1.1.1k 2021-03-25 3
OCSP(1SSL) OpenSSL OCSP(1SSL)
-rsigner file
The certificate to sign OCSP responses with.
-rother file
Additional certificates to include in the OCSP response.
-resp_no_certs
Don’t include any certificates in the OCSP response.
-resp_key_id
Identify the signer certificate using the key ID, default is to use the subject name.
-rkey file
The private key to sign OCSP responses with: if not present the file specified in the rsigner option is
used.
-rsigopt nm:v
Pass options to the signature algorithm when signing OCSP responses. Names and values of these
options are algorithm-specific.
-port portnum
Port to listen for OCSP requests on. The port may also be specified using the url option.
-ignore_err
Ignore malformed requests or responses: When acting as an OCSP client, retry if a malformed response
is received. When acting as an OCSP responder, continue running instead of terminating upon
receiving a malformed request.
-nrequest number
The OCSP server will exit after receiving number requests, default unlimited.
-nmin minutes, -ndays days
Number of minutes or days when fresh revocation information is available: used in the nextUpdate
field. If neither option is present then the nextUpdate field is omitted meaning fresh revocation
information is immediately available.
OCSP Response verification.
OCSP Response follows the rules specified in RFC2560.
Initially the OCSP responder certificate is located and the signature on the OCSP request checked using the
responder certificate’s public key.
Then a normal certificate verify is performed on the OCSP 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
CAfile and CApath options or they will be looked for in the standard OpenSSL certificates directory.
If the initial verify fails then the OCSP verify process halts with an error.
Otherwise the issuing CA certificate in the request is compared to the OCSP responder certificate: if there is
a match then the OCSP verify succeeds.
Otherwise the OCSP responder certificate’s CA is checked against the issuing CA certificate in the request.
If there is a match and the OCSPSigning extended key usage is present in the OCSP responder certificate
then the OCSP verify succeeds.
Otherwise, if -no_explicit is not set the root CA of the OCSP responders CA is checked to see if it is trusted
for OCSP signing. If it is the OCSP verify succeeds.
If none of these checks is successful then the OCSP verify fails.
What this effectively means if that if the OCSP responder certificate is authorised directly by the CA it is
issuing revocation information about (and it is correctly configured) then verification will succeed.
If the OCSP responder is a ‘‘global responder’’ which can give details about multiple CAs and has its own
separate certificate chain then its root CA can be trusted for OCSP signing. For example:
1.1.1k 2021-03-25 4
OCSP(1SSL) OpenSSL OCSP(1SSL)
1.1.1k 2021-03-25 5