Your browser does not allow this site to store cookies and other data. Some functionality on this site may not work without them. See Privacy Policy for details on how we would use cookies.

PreviousNextUp[Front page] [Index]

Options

  • -o prefix

    Saves output certificates into files with the given prefix. The prefix is first appended by a number, followed by the file extension .ca for CA certificates or .crt for user certificates.

  • -S url

    Specifies the SOCKS URL if the CA is located behind a SOCKS-enabled firewall. The format of the URL is: socks://[username@]server[:port][/network/bits[,network/bits]]

  • -H url

    Uses the given HTTP proxy server to access the CA. The format of the URL is: http://server[:port]/.

The usage line utilizes the following meta commands:

  • psk

    The pre-shared key given by the CA or RA, or a revocation password invented by the client and provided to the CA when the user wishes to revoke the certificate issued. The type and need for this depends on the PKI platform used by the CA.

    • -p key

      An authentication password or a revocation password transferred (in encrypted format) to the CA for certification request or revocation request authorization purposes.

  • keypair

    The subject key pair to be certified.

    • -P url

      URL specifying the private key location. This is an external key URL whose format is specified in Section Synopsis.

  • ca

    The CA/RA certificates.

    • -C file

      When performing enrollment, reads the CA certificate from the given file path.

    • -E file

      Optionally specifies the RA encryption certificate.

    • -V file

      Optionally specifies the RA signing certificate.

  • template

    The subject name and flags to be certified.

    • -T file

      The file containing the certificate used as the template for the operation. Values used to identify the subject are read from this, but the user may overwrite the key, key-usage flags, or subject names.

    • -s subject-ldap[;type=value]*

      A subject name in reverse LDAP format, that is, the most general component first, and alternative subject names. The name subject-ldap will be copied into the request verbatim.

      A typical choice would be a DN in the format "C=US,O=SSH,CN=Some Body", but in principle this can be anything that is usable for the resulting certificate.

      The possible type values are ip, email, dn, dns, uri, and rid.

    • -u key-usage-name[;key-usage-name]*

      Requested key usage purpose code. The following codes are recognized: digitalSignature, nonRepudiation, keyEncipherment, dataEncipherment, keyAgreement, keyCertSign, cRLSign, encipherOnly, decipherOnly, and help. The special keyword help lists the supported key usages which are defined in RFC 3280.

    • -U extended-key-usage-name[;extended-key-usage-name]*

      Requested extended key usage code. The following codes, in addition to user-specified dotted OID values are recognized: serverAuth, clientAuth, codeSigning, emailProtection, timeStamping, ikeIntermediate, and smartCardLogon.

  • access

    Specifies the CA's address in URL format. If the host address is an IPv6 address, it must be enclosed in brackets (http://[IPv6-address]:port/).

  • name

    Specifies the destination CA name.


PreviousNextUp[Front page] [Index]

===AUTO_SCHEMA_MARKUP===