STRONGSWAN_PKI---ISSUE(1)

📦
version 6.0.7 · 4 versions
, in fedora 43, fedora 44

✨ pki --issue ✨

okay so bestie, welcome to the PKI --ISSUE(1) page 💖 this is the strongSwan corner of the world where we make certificates, and honestly? it's giving main character energy 👑

🌸 NAME 🌸

pki --issue — Issue a certificate using a CA certificate and key 💅

🦋 SYNOPSIS 🦋

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 💜

So this is a sub-command of pki(1), and what it does is issue a certificate using a CA certificate and a private key 🎀 like, you bring the CA stuff, it hands you a shiny new cert. iconic behavior fr fr.

✨ OPTIONS ✨

  • -h, --help — prints usage info plus a lil summary of all the options you can use 🫶
  • -v, --debug level — sets the debug level, default is 1 🐛
  • -+, --options file — reads your command line options from a file, so you don't gotta type forever 📄
  • -i, --in file — the public key or PKCS#10 certificate request file you wanna issue. If you don't give this, the key/request gets read from STDIN 👀
  • -t, --type type — the type of the input. Pick 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 — the CA private key file. You need either this or --cakeyid, no skipping 🔑
  • -x, --cakeyid hex — smartcard or TPM CA private key object handle in hex format, with an optional 0x prefix. You need either this or --cakey 🔐
  • -c, --cacert file — the CA certificate file. Required. no cap, you literally can't skip this one ⚠️
  • -d, --dn subject-dn — the subject distinguished name (DN) of the certificate you're issuing 🏷️
  • -a, --san subjectAltName — the subjectAltName extension to include in the cert. You can use this multiple times, stack 'em up 💅
  • -l, --lifetime days — how many days the certificate stays valid, default: 1095. It gets ignored if you give both an absolute start and end time ⏳
  • -F, --not-before datetime — the absolute time when the certificate's validity begins. The datetime format is defined by the --dateform option 🕰️
  • -T, --not-after datetime — the absolute time when the certificate's validity ends. The datetime format is defined by the --dateform option ⌛
  • -D, --dateform form — the strptime(3) format for the --not-before and --not-after options, default: %d.%m.%y %T 📅
  • -s, --serial hex — serial number in hex. It's randomly allocated by default, so if you don't care, the universe picks for you 🎲
  • -e, --flag flag — adds an 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 🚩
  • -g, --digest digest — the 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 — the padding to use for RSA signatures. Either pkcs1 or pss, defaults to pkcs1 🧱
  • -f, --outform encoding — the encoding of the created certificate file. Either der (ASN.1 DER) or pem (Base64 PEM), defaults to der 📦
  • -b, --ca — includes the CA basicConstraint extension in the certificate 👑
  • -u, --crl uri — the CRL distribution point URI to include in the certificate. Can be used multiple times 🔗
  • -I, --crlissuer issuer — optional CRL issuer for the CRL at the preceding distribution point 📌
  • -o, --ocsp uri — the OCSP AuthorityInfoAccess URI to include in the certificate. Can be used multiple times 🌐
  • -p, --pathlen len — sets the path length constraint 📏
  • -B, --addrblock block — RFC 3779 address block to include in the 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 🧮
  • -n, --nc-permitted name — adds a permitted NameConstraint extension to the 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 — adds an excluded NameConstraint extension to the 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 — adds a critical extension with the given OID 🚨
  • -M, --policy-mapping issuer-oid:subject-oid — adds a policyMapping from issuer to subject OID 🗺️
  • -E, --policy-explicit len — adds a requireExplicitPolicy constraint 📢
  • -H, --policy-inhibit len — adds an inhibitPolicyMapping constraint 🛑
  • -A, --policy-any len — adds an inhibitAnyPolicy constraint 🚫

🎀 Certificate Policy 🎀

You can add multiple certificatePolicy extensions. Each one carries the following info, bestie:

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

🌈 EXAMPLES 🌈

To save on repetitive typing (the struggle is real 😭), command line options can be stored in files. 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

slay. one line, whole cert. 💅

⭐ SEE ALSO ⭐

and that's the whole page, bestie 🫶 this was strongSwan version 6.0.7, dated 2019-05-06 — go forth and issue those certificates, you absolute icon 👑💖✨

📦 where this page comes from