{ "mode": "man", "parameter": "openssl-cmp", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/openssl-cmp/1/json", "generated": "2026-08-14T01:52:10Z", "synopsis": "openssl cmp [-help] [-config filename] [-section names] [-verbosity level]\nGeneric message options:\n[-cmd ir|cr|kur|p10cr|rr|genm] [-infotype name] [-geninfo OID:int:N]\nCertificate enrollment options:\n[-newkey filename|uri] [-newkeypass arg] [-subject name] [-issuer name] [-days number]\n[-reqexts name] [-sans spec] [-sannodefault] [-policies name] [-policyoids names]\n[-policyoidscritical] [-popo number] [-csr filename] [-outtrusted filenames|uris]\n[-implicitconfirm] [-disableconfirm] [-certout filename] [-chainout filename]\nCertificate enrollment and revocation options:\n[-oldcert filename|uri] [-revreason number]\nMessage transfer options:\n[-server [http[s]://][userinfo@]host[:port][/path][?query][#fragment]] [-proxy\n[http[s]://][userinfo@]host[:port][/path][?query][#fragment]] [-noproxy addresses]\n[-recipient name] [-path remotepath] [-keepalive value] [-msgtimeout seconds]\n[-totaltimeout seconds]\nServer authentication options:\n[-trusted filenames|uris] [-untrusted filenames|uris] [-srvcert filename|uri] [-expectsender\nname] [-ignorekeyusage] [-unprotectederrors] [-extracertsout filename] [-cacertsout\nfilename]\nClient authentication and protection options:\n[-ref value] [-secret arg] [-cert filename|uri] [-owntrusted filenames|uris] [-key\nfilename|uri] [-keypass arg] [-digest name] [-mac name] [-extracerts filenames|uris]\n[-unprotectedrequests]\nCredentials format options:\n[-certform PEM|DER] [-keyform PEM|DER|P12|ENGINE] [-otherpass arg] [-engine id] [-provider\nname] [-provider-path path] [-propquery propq]\nRandom state options:\n[-rand files] [-writerand file]\nTLS connection options:\n[-tlsused] [-tlscert filename|uri] [-tlskey filename|uri] [-tlskeypass arg] [-tlsextra\nfilenames|uris] [-tlstrusted filenames|uris] [-tlshost name]\nClient-side debugging options:\n[-batch] [-repeat number] [-reqin filenames] [-reqinnewtid] [-reqout filenames] [-rspin\nfilenames] [-rspout filenames] [-usemocksrv]\nMock server options:\n[-port number] [-maxmsgs number] [-srvref value] [-srvsecret arg] [-srvcert filename|uri]\n[-srvkey filename|uri] [-srvkeypass arg] [-srvtrusted filenames|uris] [-srvuntrusted\nfilenames|uris] [-rspcert filename|uri] [-rspextracerts filenames|uris] [-rspcapubs\nfilenames|uris] [-pollcount number] [-checkafter number] [-grantimplicitconf] [-pkistatus\nnumber] [-failure number] [-failurebits number] [-statusstring arg] [-senderror]\n[-sendunprotected] [-sendunproterr] [-acceptunprotected] [-acceptunproterr]\n[-acceptraverified]\nCertificate verification options, for both CMP and TLS:\n[-allowproxycerts] [-attime timestamp] [-nochecktime] [-checksssig] [-crlcheck]\n[-crlcheckall] [-explicitpolicy] [-extendedcrl] [-ignorecritical] [-inhibitany]\n[-inhibitmap] [-partialchain] [-policy arg] [-policycheck] [-policyprint] [-purpose\npurpose] [-suiteB128] [-suiteB128only] [-suiteB192] [-trustedfirst] [-noaltchains]\n[-usedeltas] [-authlevel num] [-verifydepth num] [-verifyemail email] [-verifyhostname\nhostname] [-verifyip ip] [-verifyname name] [-x509strict] [-issuerchecks]", "sections": { "NAME": { "content": "openssl-cmp - Certificate Management Protocol (CMP, RFC 4210) application\n", "subsections": [] }, "SYNOPSIS": { "content": "openssl cmp [-help] [-config filename] [-section names] [-verbosity level]\n\nGeneric message options:\n\n[-cmd ir|cr|kur|p10cr|rr|genm] [-infotype name] [-geninfo OID:int:N]\n\nCertificate enrollment options:\n\n[-newkey filename|uri] [-newkeypass arg] [-subject name] [-issuer name] [-days number]\n[-reqexts name] [-sans spec] [-sannodefault] [-policies name] [-policyoids names]\n[-policyoidscritical] [-popo number] [-csr filename] [-outtrusted filenames|uris]\n[-implicitconfirm] [-disableconfirm] [-certout filename] [-chainout filename]\n\nCertificate enrollment and revocation options:\n\n[-oldcert filename|uri] [-revreason number]\n\nMessage transfer options:\n\n[-server [http[s]://][userinfo@]host[:port][/path][?query][#fragment]] [-proxy\n[http[s]://][userinfo@]host[:port][/path][?query][#fragment]] [-noproxy addresses]\n[-recipient name] [-path remotepath] [-keepalive value] [-msgtimeout seconds]\n[-totaltimeout seconds]\n\nServer authentication options:\n\n[-trusted filenames|uris] [-untrusted filenames|uris] [-srvcert filename|uri] [-expectsender\nname] [-ignorekeyusage] [-unprotectederrors] [-extracertsout filename] [-cacertsout\nfilename]\n\nClient authentication and protection options:\n\n[-ref value] [-secret arg] [-cert filename|uri] [-owntrusted filenames|uris] [-key\nfilename|uri] [-keypass arg] [-digest name] [-mac name] [-extracerts filenames|uris]\n[-unprotectedrequests]\n\nCredentials format options:\n\n[-certform PEM|DER] [-keyform PEM|DER|P12|ENGINE] [-otherpass arg] [-engine id] [-provider\nname] [-provider-path path] [-propquery propq]\n\nRandom state options:\n\n[-rand files] [-writerand file]\n\nTLS connection options:\n\n[-tlsused] [-tlscert filename|uri] [-tlskey filename|uri] [-tlskeypass arg] [-tlsextra\nfilenames|uris] [-tlstrusted filenames|uris] [-tlshost name]\n\nClient-side debugging options:\n\n[-batch] [-repeat number] [-reqin filenames] [-reqinnewtid] [-reqout filenames] [-rspin\nfilenames] [-rspout filenames] [-usemocksrv]\n\nMock server options:\n\n[-port number] [-maxmsgs number] [-srvref value] [-srvsecret arg] [-srvcert filename|uri]\n[-srvkey filename|uri] [-srvkeypass arg] [-srvtrusted filenames|uris] [-srvuntrusted\nfilenames|uris] [-rspcert filename|uri] [-rspextracerts filenames|uris] [-rspcapubs\nfilenames|uris] [-pollcount number] [-checkafter number] [-grantimplicitconf] [-pkistatus\nnumber] [-failure number] [-failurebits number] [-statusstring arg] [-senderror]\n[-sendunprotected] [-sendunproterr] [-acceptunprotected] [-acceptunproterr]\n[-acceptraverified]\n\nCertificate verification options, for both CMP and TLS:\n\n[-allowproxycerts] [-attime timestamp] [-nochecktime] [-checksssig] [-crlcheck]\n[-crlcheckall] [-explicitpolicy] [-extendedcrl] [-ignorecritical] [-inhibitany]\n[-inhibitmap] [-partialchain] [-policy arg] [-policycheck] [-policyprint] [-purpose\npurpose] [-suiteB128] [-suiteB128only] [-suiteB192] [-trustedfirst] [-noaltchains]\n[-usedeltas] [-authlevel num] [-verifydepth num] [-verifyemail email] [-verifyhostname\nhostname] [-verifyip ip] [-verifyname name] [-x509strict] [-issuerchecks]\n", "subsections": [] }, "DESCRIPTION": { "content": "The cmp command is a client implementation for the Certificate Management Protocol (CMP) as\ndefined in RFC4210. It can be used to request certificates from a CA server, update their\ncertificates, request certificates to be revoked, and perform other types of CMP requests.\n", "subsections": [] }, "OPTIONS": { "content": "", "subsections": [ { "name": "-help", "content": "Display a summary of all options\n" }, { "name": "-config _", "content": "Configuration file to use. An empty string \"\" means none. Default filename is from the\nenvironment variable \"OPENSSLCONF\".\n" }, { "name": "-section _", "content": "Section(s) to use within config file defining CMP options. An empty string \"\" means no\nspecific section. Default is \"cmp\".\n\nMultiple section names may be given, separated by commas and/or whitespace (where in the\nlatter case the whole argument must be enclosed in \"...\"). Contents of sections named\nlater may override contents of sections named before. In any case, as usual, the\n\"[default]\" section and finally the unnamed section (as far as present) can provide per-\noption fallback values.\n" }, { "name": "-verbosity _", "content": "Level of verbosity for logging, error output, etc. 0 = EMERG, 1 = ALERT, 2 = CRIT, 3 =\nERR, 4 = WARN, 5 = NOTE, 6 = INFO, 7 = DEBUG, 8 = TRACE. Defaults to 6 = INFO.\n" }, { "name": "Generic message options", "content": "" }, { "name": "-cmd _", "content": "CMP command to execute. Currently implemented commands are:\n\nir - Initialization Request\ncr - Certificate Request\np10cr - PKCS#10 Certification Request (for legacy support)\nkur - Key Update Request\nrr - Revocation Request\ngenm - General Message\n\nir requests initialization of an end entity into a PKI hierarchy by issuing a first\ncertificate.\n\ncr requests issuing an additional certificate for an end entity already initialized to\nthe PKI hierarchy.\n\np10cr requests issuing an additional certificate similarly to cr but using legacy PKCS#10\nCSR format.\n\nkur requests a (key) update for an existing certificate.\n\nrr requests revocation of an existing certificate.\n\ngenm requests information using a General Message, where optionally included\nInfoTypeAndValues may be used to state which info is of interest. Upon receipt of the\nGeneral Response, information about all received ITAV infoTypes is printed to stdout.\n" }, { "name": "-infotype _", "content": "Set InfoType name to use for requesting specific info in genm, e.g., \"signKeyPairTypes\".\n" }, { "name": "-geninfo _", "content": "generalInfo integer values to place in request PKIHeader with given OID, e.g.,\n\"1.2.3.4:int:56789\".\n" }, { "name": "Certificate enrollment options", "content": "" }, { "name": "-newkey _", "content": "The source of the private or public key for the certificate being requested. Defaults to\nthe public key in the PKCS#10 CSR given with the -csr option, the public key of the\nreference certificate, or the current client key.\n\nThe public portion of the key is placed in the certification request.\n\nUnless -cmd p10cr, -popo -1, or -popo 0 is given, the private key will be needed as well\nto provide the proof of possession (POPO), where the -key option may provide a fallback.\n" }, { "name": "-newkeypass _", "content": "Pass phrase source for the key given with the -newkey option. If not given here, the\npassword will be prompted for if needed.\n\nFor more information about the format of arg see openssl-passphrase-options(1).\n" }, { "name": "-subject _", "content": "X509 Distinguished Name (DN) of subject to use in the requested certificate template. If\nthe NULL-DN (\"/\") is given then no subject is placed in the template. Default is the\nsubject DN of any PKCS#10 CSR given with the -csr option. For KUR, a further fallback is\nthe subject DN of the reference certificate (see -oldcert) if provided. This fallback is\nused for IR and CR only if no SANs are set.\n\nIf provided and neither -cert nor -oldcert is given, the subject DN is used as fallback\nsender of outgoing CMP messages.\n\nThe argument must be formatted as /type0=value0/type1=value1/type2=.... Special\ncharacters may be escaped by \"\\\" (backslash); whitespace is retained. Empty values are\npermitted, but the corresponding type will not be included. Giving a single \"/\" will\nlead to an empty sequence of RDNs (a NULL-DN). Multi-valued RDNs can be formed by\nplacing a \"+\" character instead of a \"/\" between the AttributeValueAssertions (AVAs) that\nspecify the members of the set. Example:\n\n\"/DC=org/DC=OpenSSL/DC=users/UID=123456+CN=John Doe\"\n" }, { "name": "-issuer _", "content": "X509 issuer Distinguished Name (DN) of the CA server to place in the requested\ncertificate template in IR/CR/KUR. If the NULL-DN (\"/\") is given then no issuer is\nplaced in the template.\n\nIf provided and neither -recipient nor -srvcert is given, the issuer DN is used as\nfallback recipient of outgoing CMP messages.\n\nThe argument must be formatted as /type0=value0/type1=value1/type2=.... For details see\nthe description of the -subject option.\n" }, { "name": "-days _", "content": "Number of days the new certificate is requested to be valid for, counting from the\ncurrent time of the host. Also triggers the explicit request that the validity period\nstarts from the current time (as seen by the host).\n" }, { "name": "-reqexts _", "content": "Name of section in OpenSSL config file defining certificate request extensions. If the\n-csr option is present, these extensions augment the extensions contained the given\nPKCS#10 CSR, overriding any extensions with same OIDs.\n" }, { "name": "-sans _", "content": "One or more IP addresses, DNS names, or URIs separated by commas or whitespace (where in\nthe latter case the whole argument must be enclosed in \"...\") to add as Subject\nAlternative Name(s) (SAN) certificate request extension. If the special element\n\"critical\" is given the SANs are flagged as critical. Cannot be used if any Subject\nAlternative Name extension is set via -reqexts.\n" }, { "name": "-san_nodefault", "content": "When Subject Alternative Names are not given via -sans nor defined via -reqexts, they are\ncopied by default from the reference certificate (see -oldcert). This can be disabled by\ngiving the -sannodefault option.\n" }, { "name": "-policies _", "content": "Name of section in OpenSSL config file defining policies to be set as certificate request\nextension. This option cannot be used together with -policyoids.\n" }, { "name": "-policy_oids _", "content": "One or more OID(s), separated by commas and/or whitespace (where in the latter case the\nwhole argument must be enclosed in \"...\") to add as certificate policies request\nextension. This option cannot be used together with -policies.\n" }, { "name": "-policy_oids_critical", "content": "Flag the policies given with -policyoids as critical.\n" }, { "name": "-popo _", "content": "Proof-of-possession (POPO) method to use for IR/CR/KUR; values: -1..<2> where -1 = NONE,\n0 = RAVERIFIED, 1 = SIGNATURE (default), 2 = KEYENC.\n\nNote that a signature-based POPO can only be produced if a private key is provided via\nthe -newkey or -key options.\n" }, { "name": "-csr _", "content": "PKCS#10 CSR in PEM or DER format containing a certificate request. With -cmd p10cr it is\nused directly in a legacy P10CR message.\n\nWhen used with -cmd ir, cr, or kur, it is transformed into the respective regular CMP\nrequest. In this case, a private key must be provided (with -newkey or -key) for the\nproof of possession (unless -popo -1 or -popo 0 is used) and the respective public key is\nplaced in the certification request (rather than taking over the public key contained in\nthe PKCS#10 CSR).\n\nPKCS#10 CSR input may also be used with -cmd rr to specify the certificate to be revoked\nvia the included subject name and public key.\n" }, { "name": "-out_trusted _", "content": "Trusted certificate(s) to use for validating the newly enrolled certificate. During this\nverification, any certificate status checking is disabled.\n\nMultiple sources may be given, separated by commas and/or whitespace (where in the latter\ncase the whole argument must be enclosed in \"...\"). Each source may contain multiple\ncertificates.\n\nThe certificate verification options -verifyhostname, -verifyip, and -verifyemail only\naffect the certificate verification enabled via this option.\n" }, { "name": "-implicit_confirm", "content": "Request implicit confirmation of newly enrolled certificates.\n" }, { "name": "-disable_confirm", "content": "Do not send certificate confirmation message for newly enrolled certificate without\nrequesting implicit confirmation to cope with broken servers not supporting implicit\nconfirmation correctly. WARNING: This leads to behavior violating RFC 4210.\n" }, { "name": "-certout _", "content": "The file where the newly enrolled certificate should be saved.\n" }, { "name": "-chainout _", "content": "The file where the chain of the newly enrolled certificate should be saved.\n" }, { "name": "Certificate enrollment and revocation options", "content": "" }, { "name": "-oldcert _", "content": "The certificate to be updated (i.e., renewed or re-keyed) in Key Update Request (KUR)\nmessages or to be revoked in Revocation Request (RR) messages. For KUR the certificate\nto be updated defaults to -cert, and the resulting certificate is called reference\ncertificate. For RR the certificate to be revoked can also be specified using -csr.\n\nThe reference certificate, if any, is also used for deriving default subject DN and\nSubject Alternative Names and the default issuer entry in the requested certificate\ntemplate of an IR/CR/KUR. Its public key is used as a fallback in the template of\ncertification requests. Its subject is used as sender of outgoing messages if -cert is\nnot given. Its issuer is used as default recipient in CMP message headers if neither\n-recipient, -srvcert, nor -issuer is given.\n" }, { "name": "-revreason _", "content": "Set CRLReason to be included in revocation request (RR); values: 0..10 or -1 for none\n(which is the default).\n\nReason numbers defined in RFC 5280 are:\n\nCRLReason ::= ENUMERATED {\nunspecified (0),\nkeyCompromise (1),\ncACompromise (2),\naffiliationChanged (3),\nsuperseded (4),\ncessationOfOperation (5),\ncertificateHold (6),\n-- value 7 is not used\nremoveFromCRL (8),\nprivilegeWithdrawn (9),\naACompromise (10)\n}\n" }, { "name": "Message transfer options", "content": "" }, { "name": "-server _", "content": "The DNS hostname or IP address and optionally port of the CMP server to connect to using\nHTTP(S). This option excludes -port and -usemocksrv. It is ignored if -rspin is given\nwith enough filename arguments.\n\nThe scheme \"https\" may be given only if the -tlsused option is used. In this case the\ndefault port is 443, else 80. The optional userinfo and fragment components are ignored.\nAny given query component is handled as part of the path component. If a path is\nincluded it provides the default value for the -path option.\n" }, { "name": "-proxy _", "content": "The HTTP(S) proxy server to use for reaching the CMP server unless -noproxy applies, see\nbelow. The proxy port defaults to 80 or 443 if the scheme is \"https\"; apart from that\nthe optional \"http://\" or \"https://\" prefix is ignored (note that TLS may be selected by\n-tlsused), as well as any path, userinfo, and query, and fragment components. Defaults\nto the environment variable \"httpproxy\" if set, else \"HTTPPROXY\" in case no TLS is\nused, otherwise \"httpsproxy\" if set, else \"HTTPSPROXY\". This option is ignored if\n-server is not given.\n" }, { "name": "-no_proxy _", "content": "List of IP addresses and/or DNS names of servers not to use an HTTP(S) proxy for,\nseparated by commas and/or whitespace (where in the latter case the whole argument must\nbe enclosed in \"...\"). Default is from the environment variable \"noproxy\" if set, else\n\"NOPROXY\". This option is ignored if -server is not given.\n" }, { "name": "-recipient _", "content": "Distinguished Name (DN) to use in the recipient field of CMP request message headers,\ni.e., the CMP server (usually the addressed CA).\n\nThe recipient field in the header of a CMP message is mandatory. If not given explicitly\nthe recipient is determined in the following order: the subject of the CMP server\ncertificate given with the -srvcert option, the -issuer option, the issuer of the\ncertificate given with the -oldcert option, the issuer of the CMP client certificate\n(-cert option), as far as any of those is present, else the NULL-DN as last resort.\n\nThe argument must be formatted as /type0=value0/type1=value1/type2=.... For details see\nthe description of the -subject option.\n" }, { "name": "-path _", "content": "HTTP path at the CMP server (aka CMP alias) to use for POST requests. Defaults to any\npath given with -server, else \"/\".\n" }, { "name": "-keep_alive _", "content": "If the given value is 0 then HTTP connections are not kept open after receiving a\nresponse, which is the default behavior for HTTP 1.0. If the value is 1 or 2 then\npersistent connections are requested. If the value is 2 then persistent connections are\nrequired, i.e., in case the server does not grant them an error occurs. The default\nvalue is 1, which means preferring to keep the connection open.\n" }, { "name": "-msg_timeout _", "content": "Number of seconds a CMP request-response message round trip is allowed to take before a\ntimeout error is returned. A value <= 0 means no limitation (waiting indefinitely).\nDefault is to use the -totaltimeout setting.\n" }, { "name": "-total_timeout _", "content": "Maximum total number of seconds a transaction may take, including polling etc. A value\n<= 0 means no limitation (waiting indefinitely). Default is 0.\n" }, { "name": "Server authentication options", "content": "" }, { "name": "-trusted _", "content": "The certificate(s), typically of root CAs, the client shall use as trust anchors when\nvalidating signature-based protection of CMP response messages. This option is ignored\nif the -srvcert option is given as well. It provides more flexibility than -srvcert\nbecause the CMP protection certificate of the server is not pinned but may be any\ncertificate from which a chain to one of the given trust anchors can be constructed.\n\nIf none of -trusted, -srvcert, and -secret is given, message validation errors will be\nthrown unless -unprotectederrors permits an exception.\n\nMultiple sources may be given, separated by commas and/or whitespace (where in the latter\ncase the whole argument must be enclosed in \"...\"). Each source may contain multiple\ncertificates.\n\nThe certificate verification options -verifyhostname, -verifyip, and -verifyemail have\nno effect on the certificate verification enabled via this option.\n" }, { "name": "-untrusted _", "content": "Non-trusted intermediate CA certificate(s). Any extra certificates given with the -cert\noption are appended to it. All these certificates may be useful for cert path\nconstruction for the own CMP signer certificate (to include in the extraCerts field of\nrequest messages) and for the TLS client certificate (if TLS is enabled) as well as for\nchain building when validating server certificates (checking signature-based CMP message\nprotection) and when validating newly enrolled certificates.\n\nMultiple filenames or URLs may be given, separated by commas and/or whitespace. Each\nsource may contain multiple certificates.\n" }, { "name": "-srvcert _", "content": "The specific CMP server certificate to expect and directly trust (even if it is expired)\nwhen verifying signature-based protection of CMP response messages. This pins the\naccepted server and results in ignoring the -trusted option.\n\nIf set, the subject of the certificate is also used as default value for the recipient of\nCMP requests and as default value for the expected sender of CMP responses.\n" }, { "name": "-expect_sender _", "content": "Distinguished Name (DN) expected in the sender field of incoming CMP messages. Defaults\nto the subject DN of the pinned -srvcert, if any.\n\nThis can be used to make sure that only a particular entity is accepted as CMP message\nsigner, and attackers are not able to use arbitrary certificates of a trusted PKI\nhierarchy to fraudulently pose as a CMP server. Note that this option gives slightly\nmore freedom than setting the -srvcert, which pins the server to the holder of a\nparticular certificate, while the expected sender name will continue to match after\nupdates of the server cert.\n\nThe argument must be formatted as /type0=value0/type1=value1/type2=.... For details see\nthe description of the -subject option.\n" }, { "name": "-ignore_keyusage", "content": "Ignore key usage restrictions in CMP signer certificates when validating signature-based\nprotection of incoming CMP messages. By default, \"digitalSignature\" must be allowed by\nCMP signer certificates.\n" }, { "name": "-unprotected_errors", "content": "Accept missing or invalid protection of negative responses from the server. This applies\nto the following message types and contents:\n\n• error messages\n\n• negative certificate responses (IP/CP/KUP)\n\n• negative revocation responses (RP)\n\n• negative PKIConf messages\n\nWARNING: This setting leads to unspecified behavior and it is meant exclusively to allow\ninteroperability with server implementations violating RFC 4210, e.g.:\n\n• section 5.1.3.1 allows exceptions from protecting only for special cases: \"There MAY\nbe cases in which the PKIProtection BIT STRING is deliberately not used to protect a\nmessage [...] because other protection, external to PKIX, will be applied instead.\"\n\n• section 5.3.21 is clear on ErrMsgContent: \"The CA MUST always sign it with a\nsignature key.\"\n\n• appendix D.4 shows PKIConf message having protection\n" }, { "name": "-extracertsout _", "content": "The file where to save all certificates contained in the extraCerts field of the last\nreceived response message (except for pollRep and PKIConf).\n" }, { "name": "-cacertsout _", "content": "The file where to save any CA certificates contained in the caPubs field of the last\nreceived certificate response (i.e., IP, CP, or KUP) message.\n" }, { "name": "Client authentication options", "content": "" }, { "name": "-ref _", "content": "Reference number/string/value to use as fallback senderKID; this is required if no sender\nname can be determined from the -cert or <-subject> options and is typically used when\nauthenticating with pre-shared key (password-based MAC).\n" }, { "name": "-secret _", "content": "Provides the source of a secret value to use with MAC-based message protection. This\ntakes precedence over the -cert and -key options. The secret is used for creating MAC-\nbased protection of outgoing messages and for validating incoming messages that have MAC-\nbased protection. The algorithm used by default is Password-Based Message Authentication\nCode (PBM) as defined in RFC 4210 section 5.1.3.1.\n\nFor more information about the format of arg see openssl-passphrase-options(1).\n" }, { "name": "-cert _", "content": "The client's current CMP signer certificate. Requires the corresponding key to be given\nwith -key.\n\nThe subject and the public key contained in this certificate serve as fallback values in\nthe certificate template of IR/CR/KUR messages.\n\nThe subject of this certificate will be used as sender of outgoing CMP messages, while\nthe subject of -oldcert or -subjectName may provide fallback values.\n\nThe issuer of this certificate is used as one of the recipient fallback values and as\nfallback issuer entry in the certificate template of IR/CR/KUR messages.\n\nWhen performing signature-based message protection, this \"protection certificate\", also\ncalled \"signer certificate\", will be included first in the extraCerts field of outgoing\nmessages and the signature is done with the corresponding key. In Initialization Request\n(IR) messages this can be used for authenticating using an external entity certificate as\ndefined in appendix E.7 of RFC 4210.\n\nFor Key Update Request (KUR) messages this is also used as the certificate to be updated\nif the -oldcert option is not given.\n\nIf the file includes further certs, they are appended to the untrusted certs because they\ntypically constitute the chain of the client certificate, which is included in the\nextraCerts field in signature-protected request messages.\n" }, { "name": "-own_trusted _", "content": "If this list of certificates is provided then the chain built for the client-side CMP\nsigner certificate given with the -cert option is verified using the given certificates\nas trust anchors.\n\nMultiple sources may be given, separated by commas and/or whitespace (where in the latter\ncase the whole argument must be enclosed in \"...\"). Each source may contain multiple\ncertificates.\n\nThe certificate verification options -verifyhostname, -verifyip, and -verifyemail have\nno effect on the certificate verification enabled via this option.\n" }, { "name": "-key _", "content": "The corresponding private key file for the client's current certificate given in the\n-cert option. This will be used for signature-based message protection unless the\n-secret option indicating MAC-based protection or -unprotectedrequests is given.\n\nIt is also used as a fallback for the -newkey option with IR/CR/KUR messages.\n" }, { "name": "-keypass _", "content": "Pass phrase source for the private key given with the -key option. Also used for -cert\nand -oldcert in case it is an encrypted PKCS#12 file. If not given here, the password\nwill be prompted for if needed.\n\nFor more information about the format of arg see openssl-passphrase-options(1).\n" }, { "name": "-digest _", "content": "Specifies name of supported digest to use in RFC 4210's MSGSIGALG and as the one-way\nfunction (OWF) in \"MSGMACALG\". If applicable, this is used for message protection and\nproof-of-possession (POPO) signatures. To see the list of supported digests, use\n\"openssl list -digest-commands\". Defaults to \"sha256\".\n" }, { "name": "-mac _", "content": "Specifies the name of the MAC algorithm in \"MSGMACALG\". To get the names of supported\nMAC algorithms use \"openssl list -mac-algorithms\" and possibly combine such a name with\nthe name of a supported digest algorithm, e.g., hmacWithSHA256. Defaults to \"hmac-sha1\"\nas per RFC 4210.\n" }, { "name": "-extracerts _", "content": "Certificates to append in the extraCerts field when sending messages. They can be used\nas the default CMP signer certificate chain to include.\n\nMultiple sources may be given, separated by commas and/or whitespace (where in the latter\ncase the whole argument must be enclosed in \"...\"). Each source may contain multiple\ncertificates.\n" }, { "name": "-unprotected_requests", "content": "Send request messages without CMP-level protection.\n" }, { "name": "Credentials format options", "content": "" }, { "name": "-certform _", "content": "File format to use when saving a certificate to a file. Default value is PEM.\n" }, { "name": "-keyform _", "content": "The format of the key input; unspecified by default. See \"Format Options\" in openssl(1)\nfor details.\n" }, { "name": "-otherpass _", "content": "Pass phrase source for certificate given with the -trusted, -untrusted, -owntrusted,\n-srvcert, -outtrusted, -extracerts, -srvtrusted, -srvuntrusted, -rspextracerts,\n-rspcapubs, -tlsextra, and -tlstrusted options. If not given here, the password will\nbe prompted for if needed.\n\nFor more information about the format of arg see openssl-passphrase-options(1).\n" }, { "name": "-engine _", "content": "See \"Engine Options\" in openssl(1). This option is deprecated.\n\nAs an alternative to using this combination:\n\n-engine {engineid} -key {keyid} -keyform ENGINE\n\n... it's also possible to just give the key ID in URI form to -key, like this:\n\n-key org.openssl.engine:{engineid}:{keyid}\n\nThis applies to all options specifying keys: -key, -newkey, and -tlskey.\n" }, { "name": "Provider options", "content": "" }, { "name": "-provider _", "content": "" }, { "name": "-provider-path _", "content": "" }, { "name": "-propquery _", "content": "See \"Provider Options\" in openssl(1), provider(7), and property(7).\n" }, { "name": "Random state options", "content": "" }, { "name": "-rand _ -writerand _", "content": "See \"Random State Options\" in openssl(1) for details.\n" }, { "name": "TLS connection options", "content": "" }, { "name": "-tls_used", "content": "Enable using TLS (even when other TLS-related options are not set) for message exchange\nwith CMP server via HTTP. This option is not supported with the -port option. It is\nignored if the -server option is not given or -usemocksrv is given or -rspin is given\nwith enough filename arguments.\n\nThe following TLS-related options are ignored if -tlsused is not given or does not take\neffect.\n" }, { "name": "-tls_cert _", "content": "Client's TLS certificate. If the source includes further certs they are used (along with\n-untrusted certs) for constructing the client cert chain provided to the TLS server.\n" }, { "name": "-tls_key _", "content": "Private key for the client's TLS certificate.\n" }, { "name": "-tls_keypass _", "content": "Pass phrase source for client's private TLS key -tlskey. Also used for -tlscert in\ncase it is an encrypted PKCS#12 file. If not given here, the password will be prompted\nfor if needed.\n\nFor more information about the format of arg see openssl-passphrase-options(1).\n" }, { "name": "-tls_extra _", "content": "Extra certificates to provide to TLS server during TLS handshake\n" }, { "name": "-tls_trusted _", "content": "Trusted certificate(s) to use for validating the TLS server certificate. This implies\nhostname validation.\n\nMultiple sources may be given, separated by commas and/or whitespace (where in the latter\ncase the whole argument must be enclosed in \"...\"). Each source may contain multiple\ncertificates.\n\nThe certificate verification options -verifyhostname, -verifyip, and -verifyemail have\nno effect on the certificate verification enabled via this option.\n" }, { "name": "-tls_host _", "content": "Address to be checked during hostname validation. This may be a DNS name or an IP\naddress. If not given it defaults to the -server address.\n" }, { "name": "Client-side debugging options", "content": "" }, { "name": "-batch", "content": "Do not interactively prompt for input, for instance when a password is needed. This can\nbe useful for batch processing and testing.\n" }, { "name": "-repeat _", "content": "Invoke the command the given positive number of times with the same parameters. Default\nis one invocation.\n" }, { "name": "-reqin _", "content": "Take the sequence of CMP requests to send to the server from the given file(s) rather\nthan from the sequence of requests produced internally.\n\nThis option is ignored if the -rspin option is given because in the latter case no\nrequests are actually sent.\n\nMultiple filenames may be given, separated by commas and/or whitespace (where in the\nlatter case the whole argument must be enclosed in \"...\").\n\nThe files are read as far as needed to complete the transaction and filenames have been\nprovided. If more requests are needed, the remaining ones are taken from the items at\nthe respective position in the sequence of requests produced internally.\n\nThe client needs to update the recipNonce field in the given requests (except for the\nfirst one) in order to satisfy the checks to be performed by the server. This causes re-\nprotection (if protecting requests is required).\n" }, { "name": "-reqin_new_tid", "content": "Use a fresh transactionID for CMP request messages read using -reqin, which causes their\nreprotection (if protecting requests is required). This may be needed in case the\nsequence of requests is reused and the CMP server complains that the transaction ID has\nalready been used.\n" }, { "name": "-reqout _", "content": "Save the sequence of CMP requests created by the client to the given file(s). These\nrequests are not sent to the server if the -reqin option is used, too.\n\nMultiple filenames may be given, separated by commas and/or whitespace.\n\nFiles are written as far as needed to save the transaction and filenames have been\nprovided. If the transaction contains more requests, the remaining ones are not saved.\n" }, { "name": "-rspin _", "content": "Process the sequence of CMP responses provided in the given file(s), not contacting any\ngiven server, as long as enough filenames are provided to complete the transaction.\n\nMultiple filenames may be given, separated by commas and/or whitespace.\n\nAny server specified via the -server or -usemocksrv options is contacted only if more\nresponses are needed to complete the transaction. In this case the transaction will fail\nunless the server has been prepared to continue the already started transaction.\n" }, { "name": "-rspout _", "content": "Save the sequence of actually used CMP responses to the given file(s). These have been\nreceived from the server unless -rspin takes effect.\n\nMultiple filenames may be given, separated by commas and/or whitespace.\n\nFiles are written as far as needed to save the responses contained in the transaction and\nfilenames have been provided. If the transaction contains more responses, the remaining\nones are not saved.\n" }, { "name": "-use_mock_srv", "content": "Test the client using the internal CMP server mock-up at API level, bypassing socket-\nbased transfer via HTTP. This excludes the -server and -port options.\n" }, { "name": "Mock server options", "content": "" }, { "name": "-port _", "content": "Act as HTTP-based CMP server mock-up listening on the given port. This excludes the\n-server and -usemocksrv options. The -rspin, -rspout, -reqin, and -reqout options so\nfar are not supported in this mode.\n" }, { "name": "-max_msgs _", "content": "Maximum number of CMP (request) messages the CMP HTTP server mock-up should handle, which\nmust be nonnegative. The default value is 0, which means that no limit is imposed. In\nany case the server terminates on internal errors, but not when it detects a CMP-level\nerror that it can successfully answer with an error message.\n" }, { "name": "-srv_ref _", "content": "Reference value to use as senderKID of server in case no -srvcert is given.\n" }, { "name": "-srv_secret _", "content": "Password source for server authentication with a pre-shared key (secret).\n" }, { "name": "-srv_cert _", "content": "Certificate of the server.\n" }, { "name": "-srv_key _", "content": "Private key used by the server for signing messages.\n" }, { "name": "-srv_keypass _", "content": "Server private key (and cert) file pass phrase source.\n" }, { "name": "-srv_trusted _", "content": "Trusted certificates for client authentication.\n\nThe certificate verification options -verifyhostname, -verifyip, and -verifyemail have\nno effect on the certificate verification enabled via this option.\n" }, { "name": "-srv_untrusted _", "content": "Intermediate CA certs that may be useful when validating client certificates.\n" }, { "name": "-rsp_cert _", "content": "Certificate to be returned as mock enrollment result.\n" }, { "name": "-rsp_extracerts _", "content": "Extra certificates to be included in mock certification responses.\n" }, { "name": "-rsp_capubs _", "content": "CA certificates to be included in mock Initialization Response (IP) message.\n" }, { "name": "-poll_count _", "content": "Number of times the client must poll before receiving a certificate.\n" }, { "name": "-check_after _", "content": "The checkAfter value (number of seconds to wait) to include in poll response.\n" }, { "name": "-grant_implicitconf", "content": "Grant implicit confirmation of newly enrolled certificate.\n" }, { "name": "-pkistatus _", "content": "PKIStatus to be included in server response. Valid range is 0 (accepted) .. 6\n(keyUpdateWarning).\n" }, { "name": "-failure _", "content": "A single failure info bit number to be included in server response. Valid range is 0\n(badAlg) .. 26 (duplicateCertReq).\n" }, { "name": "-failurebits _", "content": "range is 0 .. 2^27 - 1." }, { "name": "-statusstring _", "content": "Text to be included as status string in server response.\n" }, { "name": "-send_error", "content": "Force server to reply with error message.\n" }, { "name": "-send_unprotected", "content": "Send response messages without CMP-level protection.\n" }, { "name": "-send_unprot_err", "content": "In case of negative responses, server shall send unprotected error messages, certificate\nresponses (IP/CP/KUP), and revocation responses (RP). WARNING: This setting leads to\nbehavior violating RFC 4210.\n" }, { "name": "-accept_unprotected", "content": "Accept missing or invalid protection of requests.\n" }, { "name": "-accept_unprot_err", "content": "Accept unprotected error messages from client. So far this has no effect because the\nserver does not accept any error messages.\n" }, { "name": "-accept_raverified", "content": "Accept RAVERIFED as proof of possession (POPO).\n" }, { "name": "Certificate verification options, for both CMP and TLS", "content": "-allowproxycerts, -attime, -nochecktime, -checksssig, -crlcheck, -crlcheckall," }, { "name": "-explicit_policy -extended_crl -ignore_critical -inhibit_any -inhibit_map", "content": "-noaltchains, -partialchain, -policy, -policycheck, -policyprint, -purpose, -suiteB128,\n-suiteB128only, -suiteB192, -trustedfirst, -usedeltas, -authlevel, -verifydepth,\n-verifyemail, -verifyhostname, -verifyip, -verifyname, -x509strict -issuerchecks\nSet various options of certificate chain verification. See \"Verification Options\" in\nopenssl-verification-options(1) for details.\n\nThe certificate verification options -verifyhostname, -verifyip, and -verifyemail only\naffect the certificate verification enabled via the -outtrusted option.\n" } ] }, "NOTES": { "content": "When a client obtains from a CMP server CA certificates that it is going to trust, for\ninstance via the \"caPubs\" field of a certificate response, authentication of the CMP server\nis particularly critical. So special care must be taken setting up server authentication\nusing -trusted and related options for certificate-based authentication or -secret for MAC-\nbased protection.\n\nWhen setting up CMP configurations and experimenting with enrollment options typically\nvarious errors occur until the configuration is correct and complete. When the CMP server\nreports an error the client will by default check the protection of the CMP response message.\nYet some CMP services tend not to protect negative responses. In this case the client will\nreject them, and thus their contents are not shown although they usually contain hints that\nwould be helpful for diagnostics. For assisting in such cases the CMP client offers a\nworkaround via the -unprotectederrors option, which allows accepting such negative messages.\n", "subsections": [] }, "EXAMPLES": { "content": "", "subsections": [ { "name": "Simple examples using the default OpenSSL configuration file", "content": "This CMP client implementation comes with demonstrative CMP sections in the example\nconfiguration file openssl/apps/openssl.cnf, which can be used to interact conveniently with\nthe Insta Demo CA.\n\nIn order to enroll an initial certificate from that CA it is sufficient to issue the\nfollowing shell commands.\n\nexport OPENSSLCONF=/path/to/openssl/apps/openssl.cnf\n\nopenssl genrsa -out insta.priv.pem\nopenssl cmp -section insta\n\nThis should produce the file insta.cert.pem containing a new certificate for the private key\nheld in insta.priv.pem. It can be viewed using, e.g.,\n\nopenssl x509 -noout -text -in insta.cert.pem\n\nIn case the network setup requires using an HTTP proxy it may be given as usual via the\nenvironment variable httpproxy or via the -proxy option in the configuration file or the CMP\ncommand-line argument -proxy, for example\n\n-proxy http://192.168.1.1:8080\n\nIn the Insta Demo CA scenario both clients and the server may use the pre-shared secret insta\nand the reference value 3078 to authenticate to each other.\n\nAlternatively, CMP messages may be protected in signature-based manner, where the trust\nanchor in this case is insta.ca.crt and the client may use any certificate already obtained\nfrom that CA, as specified in the [signature] section of the example configuration. This can\nbe used in combination with the [insta] section simply by\n\nopenssl cmp -section insta,signature\n\nBy default the CMP IR message type is used, yet CR works equally here. This may be specified\ndirectly at the command line:\n\nopenssl cmp -section insta -cmd cr\n\nor by referencing in addition the [cr] section of the example configuration:\n\nopenssl cmp -section insta,cr\n\nIn order to update the enrolled certificate one may call\n\nopenssl cmp -section insta,kur\n\nusing MAC-based protection with PBM or\n\nopenssl cmp -section insta,kur,signature\n\nusing signature-based protection.\n\nIn a similar way any previously enrolled certificate may be revoked by\n\nopenssl cmp -section insta,rr -trusted insta.ca.crt\n\nor\n\nopenssl cmp -section insta,rr,signature\n\nMany more options can be given in the configuration file and/or on the command line. For\ninstance, the -reqexts CLI option may refer to a section in the configuration file defining\nX.509 extensions to use in certificate requests, such as \"v3req\" in\nopenssl/apps/openssl.cnf:\n\nopenssl cmp -section insta,cr -reqexts v3req\n" }, { "name": "Certificate enrollment", "content": "The following examples do not make use of a configuration file at first. They assume that a\nCMP server can be contacted on the local TCP port 80 and accepts requests under the alias\n/pkix/.\n\nFor enrolling its very first certificate the client generates a client key and sends an\ninitial request message to the local CMP server using a pre-shared secret key for mutual\nauthentication. In this example the client does not have the CA certificate yet, so we\nspecify the name of the CA with the -recipient option and save any CA certificates that we\nmay receive in the \"capubs.pem\" file.\n\nIn below command line usage examples the \"\\\" at line ends is used just for formatting; each\nof the command invocations should be on a single line.\n\nopenssl genrsa -out clkey.pem\nopenssl cmp -cmd ir -server 127.0.0.1:80/pkix/ -recipient \"/CN=CMPserver\" \\\n-ref 1234 -secret pass:1234-5678 \\\n-newkey clkey.pem -subject \"/CN=MyName\" \\\n-cacertsout capubs.pem -certout clcert.pem\n" }, { "name": "Certificate update", "content": "Then, when the client certificate and its related key pair needs to be updated, the client\ncan send a key update request taking the certs in \"capubs.pem\" as trusted for authenticating\nthe server and using the previous cert and key for its own authentication. Then it can start\nusing the new cert and key.\n\nopenssl genrsa -out clkeynew.pem\nopenssl cmp -cmd kur -server 127.0.0.1:80/pkix/ \\\n-trusted capubs.pem \\\n-cert clcert.pem -key clkey.pem \\\n-newkey clkeynew.pem -certout clcert.pem\ncp clkeynew.pem clkey.pem\n\nThis command sequence can be repeated as often as needed.\n" }, { "name": "Requesting information from CMP server", "content": "Requesting \"all relevant information\" with an empty General Message. This prints information\nabout all received ITAV infoTypes to stdout.\n\nopenssl cmp -cmd genm -server 127.0.0.1/pkix/ -recipient \"/CN=CMPserver\" \\\n-ref 1234 -secret pass:1234-5678\n" }, { "name": "Using a custom configuration file", "content": "For CMP client invocations, in particular for certificate enrollment, usually many parameters\nneed to be set, which is tedious and error-prone to do on the command line. Therefore, the\nclient offers the possibility to read options from sections of the OpenSSL config file,\nusually called openssl.cnf. The values found there can still be extended and even overridden\nby any subsequently loaded sections and on the command line.\n\nAfter including in the configuration file the following sections:\n\n[cmp]\nserver = 127.0.0.1\npath = pkix/\ntrusted = capubs.pem\ncert = clcert.pem\nkey = clkey.pem\nnewkey = clkey.pem\ncertout = clcert.pem\n\n[init]\nrecipient = \"/CN=CMPserver\"\ntrusted =\ncert =\nkey =\nref = 1234\nsecret = pass:1234-5678-1234-567\nsubject = \"/CN=MyName\"\ncacertsout = capubs.pem\n\nthe above enrollment transactions reduce to\n\nopenssl cmp -section cmp,init\nopenssl cmp -cmd kur -newkey clkeynew.pem\n\nand the above transaction using a general message reduces to\n\nopenssl cmp -section cmp,init -cmd genm\n" } ] }, "SEE ALSO": { "content": "openssl-genrsa(1), openssl-ecparam(1), openssl-list(1), openssl-req(1), openssl-x509(1),\nx509v3config(5)\n", "subsections": [] }, "HISTORY": { "content": "The cmp application was added in OpenSSL 3.0.\n\nThe -engine option was deprecated in OpenSSL 3.0.\n", "subsections": [] }, "COPYRIGHT": { "content": "Copyright 2007-2023 The OpenSSL Project Authors. All Rights Reserved.\n\nLicensed under the Apache License 2.0 (the \"License\"). You may not use this file except in\ncompliance with the License. You can obtain a copy in the file LICENSE in the source\ndistribution or at .\n\n3.0.13 2026-07-29 OPENSSL-CMP(1SSL)", "subsections": [] } }, "summary": "openssl-cmp - Certificate Management Protocol (CMP, RFC 4210) application", "flags": [ { "flag": "", "long": null, "arg": null, "description": "Display a summary of all options" }, { "flag": "", "long": null, "arg": null, "description": "Configuration file to use. An empty string \"\" means none. Default filename is from the environment variable \"OPENSSLCONF\"." }, { "flag": "", "long": null, "arg": null, "description": "Section(s) to use within config file defining CMP options. An empty string \"\" means no specific section. Default is \"cmp\". Multiple section names may be given, separated by commas and/or whitespace (where in the latter case the whole argument must be enclosed in \"...\"). Contents of sections named later may override contents of sections named before. In any case, as usual, the \"[default]\" section and finally the unnamed section (as far as present) can provide per- option fallback values." }, { "flag": "", "long": null, "arg": null, "description": "Level of verbosity for logging, error output, etc. 0 = EMERG, 1 = ALERT, 2 = CRIT, 3 = ERR, 4 = WARN, 5 = NOTE, 6 = INFO, 7 = DEBUG, 8 = TRACE. Defaults to 6 = INFO." }, { "flag": "", "long": null, "arg": null, "description": "CMP command to execute. Currently implemented commands are: ir - Initialization Request cr - Certificate Request p10cr - PKCS#10 Certification Request (for legacy support) kur - Key Update Request rr - Revocation Request genm - General Message ir requests initialization of an end entity into a PKI hierarchy by issuing a first certificate. cr requests issuing an additional certificate for an end entity already initialized to the PKI hierarchy. p10cr requests issuing an additional certificate similarly to cr but using legacy PKCS#10 CSR format. kur requests a (key) update for an existing certificate. rr requests revocation of an existing certificate. genm requests information using a General Message, where optionally included InfoTypeAndValues may be used to state which info is of interest. Upon receipt of the General Response, information about all received ITAV infoTypes is printed to stdout." }, { "flag": "", "long": null, "arg": null, "description": "Set InfoType name to use for requesting specific info in genm, e.g., \"signKeyPairTypes\"." }, { "flag": "", "long": null, "arg": null, "description": "generalInfo integer values to place in request PKIHeader with given OID, e.g., \"1.2.3.4:int:56789\"." }, { "flag": "", "long": null, "arg": null, "description": "The source of the private or public key for the certificate being requested. Defaults to the public key in the PKCS#10 CSR given with the -csr option, the public key of the reference certificate, or the current client key. The public portion of the key is placed in the certification request. Unless -cmd p10cr, -popo -1, or -popo 0 is given, the private key will be needed as well to provide the proof of possession (POPO), where the -key option may provide a fallback." }, { "flag": "", "long": null, "arg": null, "description": "Pass phrase source for the key given with the -newkey option. If not given here, the password will be prompted for if needed. For more information about the format of arg see openssl-passphrase-options(1)." }, { "flag": "", "long": null, "arg": null, "description": "X509 Distinguished Name (DN) of subject to use in the requested certificate template. If the NULL-DN (\"/\") is given then no subject is placed in the template. Default is the subject DN of any PKCS#10 CSR given with the -csr option. For KUR, a further fallback is the subject DN of the reference certificate (see -oldcert) if provided. This fallback is used for IR and CR only if no SANs are set. If provided and neither -cert nor -oldcert is given, the subject DN is used as fallback sender of outgoing CMP messages. The argument must be formatted as /type0=value0/type1=value1/type2=.... Special characters may be escaped by \"\\\" (backslash); whitespace is retained. Empty values are permitted, but the corresponding type will not be included. Giving a single \"/\" will lead to an empty sequence of RDNs (a NULL-DN). Multi-valued RDNs can be formed by placing a \"+\" character instead of a \"/\" between the AttributeValueAssertions (AVAs) that specify the members of the set. Example: \"/DC=org/DC=OpenSSL/DC=users/UID=123456+CN=John Doe\"" }, { "flag": "", "long": null, "arg": null, "description": "X509 issuer Distinguished Name (DN) of the CA server to place in the requested certificate template in IR/CR/KUR. If the NULL-DN (\"/\") is given then no issuer is placed in the template. If provided and neither -recipient nor -srvcert is given, the issuer DN is used as fallback recipient of outgoing CMP messages. The argument must be formatted as /type0=value0/type1=value1/type2=.... For details see the description of the -subject option." }, { "flag": "", "long": null, "arg": null, "description": "Number of days the new certificate is requested to be valid for, counting from the current time of the host. Also triggers the explicit request that the validity period starts from the current time (as seen by the host)." }, { "flag": "", "long": null, "arg": null, "description": "Name of section in OpenSSL config file defining certificate request extensions. If the -csr option is present, these extensions augment the extensions contained the given PKCS#10 CSR, overriding any extensions with same OIDs." }, { "flag": "", "long": null, "arg": null, "description": "One or more IP addresses, DNS names, or URIs separated by commas or whitespace (where in the latter case the whole argument must be enclosed in \"...\") to add as Subject Alternative Name(s) (SAN) certificate request extension. If the special element \"critical\" is given the SANs are flagged as critical. Cannot be used if any Subject Alternative Name extension is set via -reqexts." }, { "flag": "", "long": null, "arg": null, "description": "When Subject Alternative Names are not given via -sans nor defined via -reqexts, they are copied by default from the reference certificate (see -oldcert). This can be disabled by giving the -sannodefault option." }, { "flag": "", "long": null, "arg": null, "description": "Name of section in OpenSSL config file defining policies to be set as certificate request extension. This option cannot be used together with -policyoids." }, { "flag": "", "long": null, "arg": null, "description": "One or more OID(s), separated by commas and/or whitespace (where in the latter case the whole argument must be enclosed in \"...\") to add as certificate policies request extension. This option cannot be used together with -policies." }, { "flag": "", "long": null, "arg": null, "description": "Flag the policies given with -policyoids as critical." }, { "flag": "", "long": null, "arg": null, "description": "Proof-of-possession (POPO) method to use for IR/CR/KUR; values: -1..<2> where -1 = NONE, 0 = RAVERIFIED, 1 = SIGNATURE (default), 2 = KEYENC. Note that a signature-based POPO can only be produced if a private key is provided via the -newkey or -key options." }, { "flag": "", "long": null, "arg": null, "description": "PKCS#10 CSR in PEM or DER format containing a certificate request. With -cmd p10cr it is used directly in a legacy P10CR message. When used with -cmd ir, cr, or kur, it is transformed into the respective regular CMP request. In this case, a private key must be provided (with -newkey or -key) for the proof of possession (unless -popo -1 or -popo 0 is used) and the respective public key is placed in the certification request (rather than taking over the public key contained in the PKCS#10 CSR). PKCS#10 CSR input may also be used with -cmd rr to specify the certificate to be revoked via the included subject name and public key." }, { "flag": "", "long": null, "arg": null, "description": "Trusted certificate(s) to use for validating the newly enrolled certificate. During this verification, any certificate status checking is disabled. Multiple sources may be given, separated by commas and/or whitespace (where in the latter case the whole argument must be enclosed in \"...\"). Each source may contain multiple certificates. The certificate verification options -verifyhostname, -verifyip, and -verifyemail only affect the certificate verification enabled via this option." }, { "flag": "", "long": null, "arg": null, "description": "Request implicit confirmation of newly enrolled certificates." }, { "flag": "", "long": null, "arg": null, "description": "Do not send certificate confirmation message for newly enrolled certificate without requesting implicit confirmation to cope with broken servers not supporting implicit confirmation correctly. WARNING: This leads to behavior violating RFC 4210." }, { "flag": "", "long": null, "arg": null, "description": "The file where the newly enrolled certificate should be saved." }, { "flag": "", "long": null, "arg": null, "description": "The file where the chain of the newly enrolled certificate should be saved." }, { "flag": "", "long": null, "arg": null, "description": "The certificate to be updated (i.e., renewed or re-keyed) in Key Update Request (KUR) messages or to be revoked in Revocation Request (RR) messages. For KUR the certificate to be updated defaults to -cert, and the resulting certificate is called reference certificate. For RR the certificate to be revoked can also be specified using -csr. The reference certificate, if any, is also used for deriving default subject DN and Subject Alternative Names and the default issuer entry in the requested certificate template of an IR/CR/KUR. Its public key is used as a fallback in the template of certification requests. Its subject is used as sender of outgoing messages if -cert is not given. Its issuer is used as default recipient in CMP message headers if neither -recipient, -srvcert, nor -issuer is given." }, { "flag": "", "long": null, "arg": null, "description": "Set CRLReason to be included in revocation request (RR); values: 0..10 or -1 for none (which is the default). Reason numbers defined in RFC 5280 are: CRLReason ::= ENUMERATED { unspecified (0), keyCompromise (1), cACompromise (2), affiliationChanged (3), superseded (4), cessationOfOperation (5), certificateHold (6), -- value 7 is not used removeFromCRL (8), privilegeWithdrawn (9), aACompromise (10) }" }, { "flag": "", "long": null, "arg": null, "description": "The DNS hostname or IP address and optionally port of the CMP server to connect to using HTTP(S). This option excludes -port and -usemocksrv. It is ignored if -rspin is given with enough filename arguments. The scheme \"https\" may be given only if the -tlsused option is used. In this case the default port is 443, else 80. The optional userinfo and fragment components are ignored. Any given query component is handled as part of the path component. If a path is included it provides the default value for the -path option." }, { "flag": "", "long": null, "arg": null, "description": "The HTTP(S) proxy server to use for reaching the CMP server unless -noproxy applies, see below. The proxy port defaults to 80 or 443 if the scheme is \"https\"; apart from that the optional \"http://\" or \"https://\" prefix is ignored (note that TLS may be selected by -tlsused), as well as any path, userinfo, and query, and fragment components. Defaults to the environment variable \"httpproxy\" if set, else \"HTTPPROXY\" in case no TLS is used, otherwise \"httpsproxy\" if set, else \"HTTPSPROXY\". This option is ignored if -server is not given." }, { "flag": "", "long": null, "arg": null, "description": "List of IP addresses and/or DNS names of servers not to use an HTTP(S) proxy for, separated by commas and/or whitespace (where in the latter case the whole argument must be enclosed in \"...\"). Default is from the environment variable \"noproxy\" if set, else \"NOPROXY\". This option is ignored if -server is not given." }, { "flag": "", "long": null, "arg": null, "description": "Distinguished Name (DN) to use in the recipient field of CMP request message headers, i.e., the CMP server (usually the addressed CA). The recipient field in the header of a CMP message is mandatory. If not given explicitly the recipient is determined in the following order: the subject of the CMP server certificate given with the -srvcert option, the -issuer option, the issuer of the certificate given with the -oldcert option, the issuer of the CMP client certificate (-cert option), as far as any of those is present, else the NULL-DN as last resort. The argument must be formatted as /type0=value0/type1=value1/type2=.... For details see the description of the -subject option." }, { "flag": "", "long": null, "arg": null, "description": "HTTP path at the CMP server (aka CMP alias) to use for POST requests. Defaults to any path given with -server, else \"/\"." }, { "flag": "", "long": null, "arg": null, "description": "If the given value is 0 then HTTP connections are not kept open after receiving a response, which is the default behavior for HTTP 1.0. If the value is 1 or 2 then persistent connections are requested. If the value is 2 then persistent connections are required, i.e., in case the server does not grant them an error occurs. The default value is 1, which means preferring to keep the connection open." }, { "flag": "", "long": null, "arg": null, "description": "Number of seconds a CMP request-response message round trip is allowed to take before a timeout error is returned. A value <= 0 means no limitation (waiting indefinitely). Default is to use the -totaltimeout setting." }, { "flag": "", "long": null, "arg": null, "description": "Maximum total number of seconds a transaction may take, including polling etc. A value <= 0 means no limitation (waiting indefinitely). Default is 0." }, { "flag": "", "long": null, "arg": null, "description": "The certificate(s), typically of root CAs, the client shall use as trust anchors when validating signature-based protection of CMP response messages. This option is ignored if the -srvcert option is given as well. It provides more flexibility than -srvcert because the CMP protection certificate of the server is not pinned but may be any certificate from which a chain to one of the given trust anchors can be constructed. If none of -trusted, -srvcert, and -secret is given, message validation errors will be thrown unless -unprotectederrors permits an exception. Multiple sources may be given, separated by commas and/or whitespace (where in the latter case the whole argument must be enclosed in \"...\"). Each source may contain multiple certificates. The certificate verification options -verifyhostname, -verifyip, and -verifyemail have no effect on the certificate verification enabled via this option." }, { "flag": "", "long": null, "arg": null, "description": "Non-trusted intermediate CA certificate(s). Any extra certificates given with the -cert option are appended to it. All these certificates may be useful for cert path construction for the own CMP signer certificate (to include in the extraCerts field of request messages) and for the TLS client certificate (if TLS is enabled) as well as for chain building when validating server certificates (checking signature-based CMP message protection) and when validating newly enrolled certificates. Multiple filenames or URLs may be given, separated by commas and/or whitespace. Each source may contain multiple certificates." }, { "flag": "", "long": null, "arg": null, "description": "The specific CMP server certificate to expect and directly trust (even if it is expired) when verifying signature-based protection of CMP response messages. This pins the accepted server and results in ignoring the -trusted option. If set, the subject of the certificate is also used as default value for the recipient of CMP requests and as default value for the expected sender of CMP responses." }, { "flag": "", "long": null, "arg": null, "description": "Distinguished Name (DN) expected in the sender field of incoming CMP messages. Defaults to the subject DN of the pinned -srvcert, if any. This can be used to make sure that only a particular entity is accepted as CMP message signer, and attackers are not able to use arbitrary certificates of a trusted PKI hierarchy to fraudulently pose as a CMP server. Note that this option gives slightly more freedom than setting the -srvcert, which pins the server to the holder of a particular certificate, while the expected sender name will continue to match after updates of the server cert. The argument must be formatted as /type0=value0/type1=value1/type2=.... For details see the description of the -subject option." }, { "flag": "", "long": null, "arg": null, "description": "Ignore key usage restrictions in CMP signer certificates when validating signature-based protection of incoming CMP messages. By default, \"digitalSignature\" must be allowed by CMP signer certificates." }, { "flag": "", "long": null, "arg": null, "description": "Accept missing or invalid protection of negative responses from the server. This applies to the following message types and contents: • error messages • negative certificate responses (IP/CP/KUP) • negative revocation responses (RP) • negative PKIConf messages WARNING: This setting leads to unspecified behavior and it is meant exclusively to allow interoperability with server implementations violating RFC 4210, e.g.: • section 5.1.3.1 allows exceptions from protecting only for special cases: \"There MAY be cases in which the PKIProtection BIT STRING is deliberately not used to protect a message [...] because other protection, external to PKIX, will be applied instead.\" • section 5.3.21 is clear on ErrMsgContent: \"The CA MUST always sign it with a signature key.\" • appendix D.4 shows PKIConf message having protection" }, { "flag": "", "long": null, "arg": null, "description": "The file where to save all certificates contained in the extraCerts field of the last received response message (except for pollRep and PKIConf)." }, { "flag": "", "long": null, "arg": null, "description": "The file where to save any CA certificates contained in the caPubs field of the last received certificate response (i.e., IP, CP, or KUP) message." }, { "flag": "", "long": null, "arg": null, "description": "Reference number/string/value to use as fallback senderKID; this is required if no sender name can be determined from the -cert or <-subject> options and is typically used when authenticating with pre-shared key (password-based MAC)." }, { "flag": "", "long": null, "arg": null, "description": "Provides the source of a secret value to use with MAC-based message protection. This takes precedence over the -cert and -key options. The secret is used for creating MAC- based protection of outgoing messages and for validating incoming messages that have MAC- based protection. The algorithm used by default is Password-Based Message Authentication Code (PBM) as defined in RFC 4210 section 5.1.3.1. For more information about the format of arg see openssl-passphrase-options(1)." }, { "flag": "", "long": null, "arg": null, "description": "The client's current CMP signer certificate. Requires the corresponding key to be given with -key. The subject and the public key contained in this certificate serve as fallback values in the certificate template of IR/CR/KUR messages. The subject of this certificate will be used as sender of outgoing CMP messages, while the subject of -oldcert or -subjectName may provide fallback values. The issuer of this certificate is used as one of the recipient fallback values and as fallback issuer entry in the certificate template of IR/CR/KUR messages. When performing signature-based message protection, this \"protection certificate\", also called \"signer certificate\", will be included first in the extraCerts field of outgoing messages and the signature is done with the corresponding key. In Initialization Request (IR) messages this can be used for authenticating using an external entity certificate as defined in appendix E.7 of RFC 4210. For Key Update Request (KUR) messages this is also used as the certificate to be updated if the -oldcert option is not given. If the file includes further certs, they are appended to the untrusted certs because they typically constitute the chain of the client certificate, which is included in the extraCerts field in signature-protected request messages." }, { "flag": "", "long": null, "arg": null, "description": "If this list of certificates is provided then the chain built for the client-side CMP signer certificate given with the -cert option is verified using the given certificates as trust anchors. Multiple sources may be given, separated by commas and/or whitespace (where in the latter case the whole argument must be enclosed in \"...\"). Each source may contain multiple certificates. The certificate verification options -verifyhostname, -verifyip, and -verifyemail have no effect on the certificate verification enabled via this option." }, { "flag": "", "long": null, "arg": null, "description": "The corresponding private key file for the client's current certificate given in the -cert option. This will be used for signature-based message protection unless the -secret option indicating MAC-based protection or -unprotectedrequests is given. It is also used as a fallback for the -newkey option with IR/CR/KUR messages." }, { "flag": "", "long": null, "arg": null, "description": "Pass phrase source for the private key given with the -key option. Also used for -cert and -oldcert in case it is an encrypted PKCS#12 file. If not given here, the password will be prompted for if needed. For more information about the format of arg see openssl-passphrase-options(1)." }, { "flag": "", "long": null, "arg": null, "description": "Specifies name of supported digest to use in RFC 4210's MSGSIGALG and as the one-way function (OWF) in \"MSGMACALG\". If applicable, this is used for message protection and proof-of-possession (POPO) signatures. To see the list of supported digests, use \"openssl list -digest-commands\". Defaults to \"sha256\"." }, { "flag": "", "long": null, "arg": null, "description": "Specifies the name of the MAC algorithm in \"MSGMACALG\". To get the names of supported MAC algorithms use \"openssl list -mac-algorithms\" and possibly combine such a name with the name of a supported digest algorithm, e.g., hmacWithSHA256. Defaults to \"hmac-sha1\" as per RFC 4210." }, { "flag": "", "long": null, "arg": null, "description": "Certificates to append in the extraCerts field when sending messages. They can be used as the default CMP signer certificate chain to include. Multiple sources may be given, separated by commas and/or whitespace (where in the latter case the whole argument must be enclosed in \"...\"). Each source may contain multiple certificates." }, { "flag": "", "long": null, "arg": null, "description": "Send request messages without CMP-level protection." }, { "flag": "", "long": null, "arg": null, "description": "File format to use when saving a certificate to a file. Default value is PEM." }, { "flag": "", "long": null, "arg": null, "description": "The format of the key input; unspecified by default. See \"Format Options\" in openssl(1) for details." }, { "flag": "", "long": null, "arg": null, "description": "Pass phrase source for certificate given with the -trusted, -untrusted, -owntrusted, -srvcert, -outtrusted, -extracerts, -srvtrusted, -srvuntrusted, -rspextracerts, -rspcapubs, -tlsextra, and -tlstrusted options. If not given here, the password will be prompted for if needed. For more information about the format of arg see openssl-passphrase-options(1)." }, { "flag": "", "long": null, "arg": null, "description": "See \"Engine Options\" in openssl(1). This option is deprecated. As an alternative to using this combination: -engine {engineid} -key {keyid} -keyform ENGINE ... it's also possible to just give the key ID in URI form to -key, like this: -key org.openssl.engine:{engineid}:{keyid} This applies to all options specifying keys: -key, -newkey, and -tlskey." }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": null, "arg": null, "description": "" }, { "flag": "", "long": null, "arg": null, "description": "See \"Provider Options\" in openssl(1), provider(7), and property(7)." }, { "flag": "", "long": null, "arg": null, "description": "See \"Random State Options\" in openssl(1) for details." }, { "flag": "", "long": null, "arg": null, "description": "Enable using TLS (even when other TLS-related options are not set) for message exchange with CMP server via HTTP. This option is not supported with the -port option. It is ignored if the -server option is not given or -usemocksrv is given or -rspin is given with enough filename arguments. The following TLS-related options are ignored if -tlsused is not given or does not take effect." }, { "flag": "", "long": null, "arg": null, "description": "Client's TLS certificate. If the source includes further certs they are used (along with -untrusted certs) for constructing the client cert chain provided to the TLS server." }, { "flag": "", "long": null, "arg": null, "description": "Private key for the client's TLS certificate." }, { "flag": "", "long": null, "arg": null, "description": "Pass phrase source for client's private TLS key -tlskey. Also used for -tlscert in case it is an encrypted PKCS#12 file. If not given here, the password will be prompted for if needed. For more information about the format of arg see openssl-passphrase-options(1)." }, { "flag": "", "long": null, "arg": null, "description": "Extra certificates to provide to TLS server during TLS handshake" }, { "flag": "", "long": null, "arg": null, "description": "Trusted certificate(s) to use for validating the TLS server certificate. This implies hostname validation. Multiple sources may be given, separated by commas and/or whitespace (where in the latter case the whole argument must be enclosed in \"...\"). Each source may contain multiple certificates. The certificate verification options -verifyhostname, -verifyip, and -verifyemail have no effect on the certificate verification enabled via this option." }, { "flag": "", "long": null, "arg": null, "description": "Address to be checked during hostname validation. This may be a DNS name or an IP address. If not given it defaults to the -server address." }, { "flag": "", "long": null, "arg": null, "description": "Do not interactively prompt for input, for instance when a password is needed. This can be useful for batch processing and testing." }, { "flag": "", "long": null, "arg": null, "description": "Invoke the command the given positive number of times with the same parameters. Default is one invocation." }, { "flag": "", "long": null, "arg": null, "description": "Take the sequence of CMP requests to send to the server from the given file(s) rather than from the sequence of requests produced internally. This option is ignored if the -rspin option is given because in the latter case no requests are actually sent. Multiple filenames may be given, separated by commas and/or whitespace (where in the latter case the whole argument must be enclosed in \"...\"). The files are read as far as needed to complete the transaction and filenames have been provided. If more requests are needed, the remaining ones are taken from the items at the respective position in the sequence of requests produced internally. The client needs to update the recipNonce field in the given requests (except for the first one) in order to satisfy the checks to be performed by the server. This causes re- protection (if protecting requests is required)." }, { "flag": "", "long": null, "arg": null, "description": "Use a fresh transactionID for CMP request messages read using -reqin, which causes their reprotection (if protecting requests is required). This may be needed in case the sequence of requests is reused and the CMP server complains that the transaction ID has already been used." }, { "flag": "", "long": null, "arg": null, "description": "Save the sequence of CMP requests created by the client to the given file(s). These requests are not sent to the server if the -reqin option is used, too. Multiple filenames may be given, separated by commas and/or whitespace. Files are written as far as needed to save the transaction and filenames have been provided. If the transaction contains more requests, the remaining ones are not saved." }, { "flag": "", "long": null, "arg": null, "description": "Process the sequence of CMP responses provided in the given file(s), not contacting any given server, as long as enough filenames are provided to complete the transaction. Multiple filenames may be given, separated by commas and/or whitespace. Any server specified via the -server or -usemocksrv options is contacted only if more responses are needed to complete the transaction. In this case the transaction will fail unless the server has been prepared to continue the already started transaction." }, { "flag": "", "long": null, "arg": null, "description": "Save the sequence of actually used CMP responses to the given file(s). These have been received from the server unless -rspin takes effect. Multiple filenames may be given, separated by commas and/or whitespace. Files are written as far as needed to save the responses contained in the transaction and filenames have been provided. If the transaction contains more responses, the remaining ones are not saved." }, { "flag": "", "long": null, "arg": null, "description": "Test the client using the internal CMP server mock-up at API level, bypassing socket- based transfer via HTTP. This excludes the -server and -port options." }, { "flag": "", "long": null, "arg": null, "description": "Act as HTTP-based CMP server mock-up listening on the given port. This excludes the -server and -usemocksrv options. The -rspin, -rspout, -reqin, and -reqout options so far are not supported in this mode." }, { "flag": "", "long": null, "arg": null, "description": "Maximum number of CMP (request) messages the CMP HTTP server mock-up should handle, which must be nonnegative. The default value is 0, which means that no limit is imposed. In any case the server terminates on internal errors, but not when it detects a CMP-level error that it can successfully answer with an error message." }, { "flag": "", "long": null, "arg": null, "description": "Reference value to use as senderKID of server in case no -srvcert is given." }, { "flag": "", "long": null, "arg": null, "description": "Password source for server authentication with a pre-shared key (secret)." }, { "flag": "", "long": null, "arg": null, "description": "Certificate of the server." }, { "flag": "", "long": null, "arg": null, "description": "Private key used by the server for signing messages." }, { "flag": "", "long": null, "arg": null, "description": "Server private key (and cert) file pass phrase source." }, { "flag": "", "long": null, "arg": null, "description": "Trusted certificates for client authentication. The certificate verification options -verifyhostname, -verifyip, and -verifyemail have no effect on the certificate verification enabled via this option." }, { "flag": "", "long": null, "arg": null, "description": "Intermediate CA certs that may be useful when validating client certificates." }, { "flag": "", "long": null, "arg": null, "description": "Certificate to be returned as mock enrollment result." }, { "flag": "", "long": null, "arg": null, "description": "Extra certificates to be included in mock certification responses." }, { "flag": "", "long": null, "arg": null, "description": "CA certificates to be included in mock Initialization Response (IP) message." }, { "flag": "", "long": null, "arg": null, "description": "Number of times the client must poll before receiving a certificate." }, { "flag": "", "long": null, "arg": null, "description": "The checkAfter value (number of seconds to wait) to include in poll response." }, { "flag": "", "long": null, "arg": null, "description": "Grant implicit confirmation of newly enrolled certificate." }, { "flag": "", "long": null, "arg": null, "description": "PKIStatus to be included in server response. Valid range is 0 (accepted) .. 6 (keyUpdateWarning)." }, { "flag": "", "long": null, "arg": null, "description": "A single failure info bit number to be included in server response. Valid range is 0 (badAlg) .. 26 (duplicateCertReq)." }, { "flag": "", "long": null, "arg": null, "description": "range is 0 .. 2^27 - 1." }, { "flag": "", "long": null, "arg": null, "description": "Text to be included as status string in server response." }, { "flag": "", "long": null, "arg": null, "description": "Force server to reply with error message." }, { "flag": "", "long": null, "arg": null, "description": "Send response messages without CMP-level protection." }, { "flag": "", "long": null, "arg": null, "description": "In case of negative responses, server shall send unprotected error messages, certificate responses (IP/CP/KUP), and revocation responses (RP). WARNING: This setting leads to behavior violating RFC 4210." }, { "flag": "", "long": null, "arg": null, "description": "Accept missing or invalid protection of requests." }, { "flag": "", "long": null, "arg": null, "description": "Accept unprotected error messages from client. So far this has no effect because the server does not accept any error messages." }, { "flag": "", "long": null, "arg": null, "description": "Accept RAVERIFED as proof of possession (POPO)." }, { "flag": "", "long": null, "arg": null, "description": "-noaltchains, -partialchain, -policy, -policycheck, -policyprint, -purpose, -suiteB128, -suiteB128only, -suiteB192, -trustedfirst, -usedeltas, -authlevel, -verifydepth, -verifyemail, -verifyhostname, -verifyip, -verifyname, -x509strict -issuerchecks Set various options of certificate chain verification. See \"Verification Options\" in openssl-verification-options(1) for details. The certificate verification options -verifyhostname, -verifyip, and -verifyemail only affect the certificate verification enabled via the -outtrusted option." } ], "examples": [ "This CMP client implementation comes with demonstrative CMP sections in the example", "configuration file openssl/apps/openssl.cnf, which can be used to interact conveniently with", "the Insta Demo CA.", "In order to enroll an initial certificate from that CA it is sufficient to issue the", "following shell commands.", "export OPENSSLCONF=/path/to/openssl/apps/openssl.cnf", "openssl genrsa -out insta.priv.pem", "openssl cmp -section insta", "This should produce the file insta.cert.pem containing a new certificate for the private key", "held in insta.priv.pem. It can be viewed using, e.g.,", "openssl x509 -noout -text -in insta.cert.pem", "In case the network setup requires using an HTTP proxy it may be given as usual via the", "environment variable httpproxy or via the -proxy option in the configuration file or the CMP", "command-line argument -proxy, for example", "-proxy http://192.168.1.1:8080", "In the Insta Demo CA scenario both clients and the server may use the pre-shared secret insta", "and the reference value 3078 to authenticate to each other.", "Alternatively, CMP messages may be protected in signature-based manner, where the trust", "anchor in this case is insta.ca.crt and the client may use any certificate already obtained", "from that CA, as specified in the [signature] section of the example configuration. This can", "be used in combination with the [insta] section simply by", "openssl cmp -section insta,signature", "By default the CMP IR message type is used, yet CR works equally here. This may be specified", "directly at the command line:", "openssl cmp -section insta -cmd cr", "or by referencing in addition the [cr] section of the example configuration:", "openssl cmp -section insta,cr", "In order to update the enrolled certificate one may call", "openssl cmp -section insta,kur", "using MAC-based protection with PBM or", "openssl cmp -section insta,kur,signature", "using signature-based protection.", "In a similar way any previously enrolled certificate may be revoked by", "openssl cmp -section insta,rr -trusted insta.ca.crt", "or", "openssl cmp -section insta,rr,signature", "Many more options can be given in the configuration file and/or on the command line. For", "instance, the -reqexts CLI option may refer to a section in the configuration file defining", "X.509 extensions to use in certificate requests, such as \"v3req\" in", "openssl/apps/openssl.cnf:", "openssl cmp -section insta,cr -reqexts v3req", "The following examples do not make use of a configuration file at first. They assume that a", "CMP server can be contacted on the local TCP port 80 and accepts requests under the alias", "/pkix/.", "For enrolling its very first certificate the client generates a client key and sends an", "initial request message to the local CMP server using a pre-shared secret key for mutual", "authentication. In this example the client does not have the CA certificate yet, so we", "specify the name of the CA with the -recipient option and save any CA certificates that we", "may receive in the \"capubs.pem\" file.", "In below command line usage examples the \"\\\" at line ends is used just for formatting; each", "of the command invocations should be on a single line.", "openssl genrsa -out clkey.pem", "openssl cmp -cmd ir -server 127.0.0.1:80/pkix/ -recipient \"/CN=CMPserver\" \\", "-ref 1234 -secret pass:1234-5678 \\", "-newkey clkey.pem -subject \"/CN=MyName\" \\", "-cacertsout capubs.pem -certout clcert.pem", "Then, when the client certificate and its related key pair needs to be updated, the client", "can send a key update request taking the certs in \"capubs.pem\" as trusted for authenticating", "the server and using the previous cert and key for its own authentication. Then it can start", "using the new cert and key.", "openssl genrsa -out clkeynew.pem", "openssl cmp -cmd kur -server 127.0.0.1:80/pkix/ \\", "-trusted capubs.pem \\", "-cert clcert.pem -key clkey.pem \\", "-newkey clkeynew.pem -certout clcert.pem", "cp clkeynew.pem clkey.pem", "This command sequence can be repeated as often as needed.", "Requesting \"all relevant information\" with an empty General Message. This prints information", "about all received ITAV infoTypes to stdout.", "openssl cmp -cmd genm -server 127.0.0.1/pkix/ -recipient \"/CN=CMPserver\" \\", "-ref 1234 -secret pass:1234-5678", "For CMP client invocations, in particular for certificate enrollment, usually many parameters", "need to be set, which is tedious and error-prone to do on the command line. Therefore, the", "client offers the possibility to read options from sections of the OpenSSL config file,", "usually called openssl.cnf. The values found there can still be extended and even overridden", "by any subsequently loaded sections and on the command line.", "After including in the configuration file the following sections:", "[cmp]", "server = 127.0.0.1", "path = pkix/", "trusted = capubs.pem", "cert = clcert.pem", "key = clkey.pem", "newkey = clkey.pem", "certout = clcert.pem", "[init]", "recipient = \"/CN=CMPserver\"", "trusted =", "cert =", "key =", "ref = 1234", "secret = pass:1234-5678-1234-567", "subject = \"/CN=MyName\"", "cacertsout = capubs.pem", "the above enrollment transactions reduce to", "openssl cmp -section cmp,init", "openssl cmp -cmd kur -newkey clkeynew.pem", "and the above transaction using a general message reduces to", "openssl cmp -section cmp,init -cmd genm" ], "see_also": [ { "name": "openssl-genrsa", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/openssl-genrsa/1/json" }, { "name": "openssl-ecparam", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/openssl-ecparam/1/json" }, { "name": "openssl-list", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/openssl-list/1/json" }, { "name": "openssl-req", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/openssl-req/1/json" }, { "name": "openssl-x509", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/openssl-x509/1/json" }, { "name": "x509v3config", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/x509v3config/5/json" } ] }