PKI---ISSUE(1)

💖 pki --issue — issue a certificate using a CA certificate and key 💖

okay bestie, this is the PKI --ISSUE(1) page — strongSwan's pki --issue sub-command. It is literally the one that issues a certificate using a CA certificate and key, and it's giving main-character PKI energy. 🎀

---

✨ NAME ✨

pki --issue — issue a certificate using a CA certificate and key. periodt, that's the name, no cap.

---

🌸 SYNOPSIS 🌸

the shapes this command can take, bestie:

pki --issue [--in file] [--type type] --cakey file|--cakeyid hex
            --cacert file [--dn subject-dn] [--san subjectAltName]
            [--lifetime days] [--not-before datetime] [--not-
            after datetime] [--serial hex] [--flag flag]
            [--digest digest] [--rsa-padding padding] [--ca]
            [--crl uri [--crlissuer issuer]] [--ocsp uri]
            [--pathlen len] [--addrblock block] [--nc-permitted name]
            [--nc-excluded name] [--critical oid]
            [--policy-mapping mapping] [--policy-explicit len]
            [--policy-inhibit len] [--policy-any len]
            [--cert-policy oid [--cps-uri uri] [--user-notice text]]
            [--outform encoding] [--debug level]

pki --issue --options file

pki --issue -h | --help

---

🦋 DESCRIPTION 🦋

This sub-command of pki(1) is used to issue a certificate using a CA certificate and private key. slay — that's the whole assignment. 💅

---

🎀 OPTIONS 🎀

• -h, --help — print usage information with a summary of the available options. ur welcome.
• -v, --debug level — set debug level, default: 1.
• -+, --options file — read command line options from file. yes, the short option is literally -+, iconic.
• -i, --in file — public key or PKCS#10 certificate request file to issue. If not given, the key/request is read from STDIN.
• -t, --type type — type of the input. One of pub (public key), priv (private key), rsa (RSA private key), ecdsa (ECDSA private key), ed25519 (Ed25519 private key), ed448 (Ed448 private key) or pkcs10 (PKCS#10 certificate request), defaults to pub.
• -k, --cakey file — CA private key file. Either this or --cakeyid is required.
• -x, --cakeyid hex — smartcard or TPM CA private key object handle in hex format with an optional 0x prefix. Either this or --cakey is required.
• -c, --cacert file — CA certificate file. Required. no skipping this one, bestie.
• -d, --dn subject-dn — subject distinguished name (DN) of the issued certificate.
• -a, --san subjectAltName — subjectAltName extension to include in certificate. Can be used multiple times. stack 'em.
• -l, --lifetime days — days the certificate is valid, default: 1095. Ignored if both an absolute start and end time are given.
• -F, --not-before datetime — absolute time when the validity of the certificate begins. The datetime format is defined by the --dateform option.
• -T, --not-after datetime — absolute time when the validity of the certificate ends. The datetime format is defined by the --dateform option.
• -D, --dateform form — strptime(3) format for the --not-before and --not-after options, default: %d.%m.%y %T.
• -s, --serial hex — serial number in hex. It is randomly allocated by default.
• -e, --flag flag — add extendedKeyUsage flag. One of serverAuth, clientAuth, crlSign, ocspSigning or msSmartcardLogon. Can be used multiple times. Without modifiers, this overrides flags from PKCS#10 certificate requests. Prefixing a flag with + adds it to the set of flags read from the request, prefixing it with - removes it from that set. the way that is so specific and so real.
• -g, --digest digest — digest to use for signature creation. One of md5, sha1, sha224, sha256, sha384, or sha512. The default is determined based on the type and size of the signature key.
• -R, --rsa-padding padding — padding to use for RSA signatures. Either pkcs1 or pss, defaults to pkcs1.
• -f, --outform encoding — encoding of the created certificate file. Either der (ASN.1 DER) or pem (Base64 PEM), defaults to der.
• -b, --ca — include CA basicConstraint extension in certificate.
• -u, --crl uri — CRL distribution point URI to include in certificate. Can be used multiple times.
• -I, --crlissuer issuer — optional CRL issuer for the CRL at the preceding distribution point.
• -o, --ocsp uri — OCSP AuthorityInfoAccess URI to include in certificate. Can be used multiple times.
• -p, --pathlen len — set path length constraint.
• -B, --addrblock block — RFC 3779 address block to include in certificate. block is either a CIDR subnet (such as 10.0.0.0/8) or an arbitrary address range (192.168.1.7-192.168.1.13). Can be repeated to include multiple blocks. Please note that the supplied blocks are included in the certificate as is, so for standards compliance, multiple blocks must be supplied in correct order and adjacent blocks must be combined. Refer to RFC 3779 for details. this one is giving "read the RFC, bestie" energy.
• -n, --nc-permitted name — add permitted NameConstraint extension to certificate. For DNS or email constraints, the identity type is not always detectable by the given name. Use the dns: or email: prefix to force a constraint type.
• -N, --nc-excluded name — add excluded NameConstraint extension to certificate. For DNS or email constraints, the identity type is not always detectable by the given name. Use the dns: or email: prefix to force a constraint type.
• -X, --critical oid — add a critical extension with the given OID.
• -M, --policy-mapping issuer-oid:subject-oid — add policyMapping from issuer to subject OID.
• -E, --policy-explicit len — add requireExplicitPolicy constraint.
• -H, --policy-inhibit len — add inhibitPolicyMapping constraint.
• -A, --policy-any len — add inhibitAnyPolicy constraint.

🧚 Certificate Policy 🧚

Multiple certificatePolicy extensions can be added. Each with the following information:

• -P, --cert-policy oid — OID to include in certificatePolicy extension. Required.
• -C, --cps-uri uri — Certification Practice statement URI for certificatePolicy.
• -U, --user-notice text — User notice for certificatePolicy.

---

🌈 EXAMPLES 🌈

To save repetitive typing, command line options can be stored in files. bestie, this is self-care. Let's assume pki.opt contains the following contents:

  --cacert ca_cert.der --cakey ca_key.der --digest sha256
  --flag serverAuth --lifetime 1460 --type pkcs10

Then the following command can be used to issue a certificate based on a given PKCS#10 certificate request and the options above:

  pki --issue --options pki.opt --in req.der > cert.der

---

👑 SEE ALSO 👑

pki(1) — the parent page, go say hi. 🫶

---

made with strongSwan 6.1.0 energy, dated 2019-05-06, and the manual name is still serving PKI --ISSUE(1) — bye bestie, slay those certs 💖✨