CA.PL(1ossl)

πŸ“¦
version 15.1 Β· 2 versions
, in freebsd 15.1

πŸŽ€ CA.PL(1ossl) β€” the friendlier-interface-for-OpenSSL-certificate-programs era πŸŽ€

okay bestie, so this is the page for CA.pl, a perl script that's basically the training-wheels-but-make-it-cute front end for openssl(1). ✨

✨ SYNOPSIS ✨

CA.pl -? | -h | -help

CA.pl -newcert | -newreq | -newreq-nodes | -xsign | -sign | -signCA |
-signcert | -crl | -newca [-extra-cmd parameter]

CA.pl -pkcs12 [certname]

CA.pl -verify certfile ...

CA.pl -revoke certfile [reason]

πŸ’– DESCRIPTION πŸ’–

So the CA.pl script is a perl script β€” literally in the name, iykyk β€” and what it does is hand the relevant command line arguments over to the openssl(1) command for a bunch of common certificate operations. Its whole personality is simplifying certificate creation and management via some simple options. πŸ¦‹

It's meant as a simple front end for the openssl(1) program, for a beginner to use. But ngl, its behaviour isn't always what's wanted 😭 β€” if you want more control over how the certificate commands behave, just call the openssl(1) command directly.

Most of the filenames mentioned below can be modified by editing the CA.pl script. πŸ™ˆ

Under some environments it may not be possible to run the CA.pl script directly (for example Win32) and the default configuration file location may be wrong. In that case, this command:

perl -S CA.pl

can be used, and the OPENSSL_CONF environment variable can be set to point to the correct path of the configuration file. πŸ’…

✨ OPTIONS ✨

  • -?, -h, -help β€” prints a usage message. that's it, that's the tea πŸ«–
  • -newcert β€” creates a new self signed certificate. the private key is written to the file newkey.pem and the request written to the file newreq.pem. invokes openssl-req(1). πŸ”₯
  • -newreq β€” creates a new certificate request. private key goes to newkey.pem, request goes to newreq.pem. executes openssl-req(1) under the hood. ✨
  • -newreq-nodes β€” like -newreq except the private key will not be encrypted. uses openssl-req(1). πŸ‘€
  • -newca β€” creates a new CA hierarchy for use with the ca program (or the -signcert and -xsign options). you get prompted to enter the filename of the CA certificates (which should also contain the private key), or by hitting ENTER details of the CA will be prompted for. the relevant files and directories are created in a directory called demoCA in the current directory. uses openssl-req(1) and openssl-ca(1). πŸ‘‘
lowkey important: if the demoCA directory already exists, then -newca will not overwrite it and will do nothing πŸ’€. this can happen if a previous call using the -newca option terminated abnormally. to get the correct behaviour, delete the directory if it already exists. πŸ—‘οΈ
  • -pkcs12 β€” creates a PKCS#12 file containing the user certificate, private key and CA certificate. it expects the user certificate and private key to be in the file newcert.pem and the CA certificate to be in the file demoCA/cacert.pem, and it creates a file newcert.p12. so you can call this command after the -sign option. the PKCS#12 file can be imported directly into a browser. 🧚 if there's an additional argument on the command line it'll be used as the "friendly name" for the certificate (which is typically displayed in the browser list box), otherwise the name "My Certificate" is used. delegates work to openssl-pkcs12(1). 🌸
  • -sign, -xsign β€” calls the openssl-ca(1) command to sign a certificate request. expects the request to be in the file newreq.pem. the new certificate is written to the file newcert.pem β€” except in the case of the -xsign option, when it's written to standard output. πŸ“€
  • -signCA β€” same as -sign except it uses the configuration file section v3_ca, and so makes the signed request a valid CA certificate. this is useful when creating an intermediate CA from a root CA. extra params are passed to openssl-ca(1). πŸ’œ
  • -signcert β€” same as -sign except it expects a self signed certificate to be present in the file newreq.pem. extra params are passed to openssl-x509(1) and openssl-ca(1). πŸŽ€
  • -crl β€” generate a CRL. executes openssl-ca(1). ⭐
  • -revoke certfile [reason] β€” revoke the certificate contained in the specified certfile. an optional reason may be specified, and it must be one of: unspecified, keyCompromise, CACompromise, affiliationChanged, superseded, cessationOfOperation, certificateHold, or removeFromCRL. leverages openssl-ca(1). 🚫
  • -verify β€” verifies certificates against the CA certificate for demoCA. if no certificates are specified on the command line it tries to verify the file newcert.pem. invokes openssl-verify(1). πŸ”
  • -extra-cmd parameter β€” for each option extra-cmd, pass parameter to the openssl(1) sub-command with the same name as cmd, if that sub-command is invoked. for example, if openssl-req(1) is invoked, the parameter given with -extra-req will be passed to it. for multi-word parameters, either repeat the option or quote the parameters so it looks like one word to your shell. see the individual command documentation for more information. 🫢

🌈 EXAMPLES 🌈

Create a CA hierarchy β€” literally one line, slay:

CA.pl -newca

Complete certificate creation example: create a CA, create a request, sign the request and finally create a PKCS#12 file containing it. the full main-character arc πŸ’…:

CA.pl -newca
CA.pl -newreq
CA.pl -sign
CA.pl -pkcs12 "My Test Certificate"

πŸ¦‹ ENVIRONMENT πŸ¦‹

  • the environment variable OPENSSL may be used to specify the name of the OpenSSL program. it can be a full pathname, or a relative one. πŸ›£οΈ
  • the environment variable OPENSSL_CONFIG may be used to specify a configuration option and value to the req and ca commands invoked by this script. its value should be the option and pathname, as in "-config /path/to/conf-file". πŸ—‚οΈ

πŸ‘‘ SEE ALSO πŸ‘‘

openssl(1), openssl-x509(1), openssl-ca(1), openssl-req(1), openssl-pkcs12(1), config(5)

Copyright 2000-2026 The OpenSSL Project Authors. All Rights Reserved.

Licensed under the Apache License 2.0 (the "License"). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE in the source distribution or at <https://www.openssl.org/source/license.html>.


okay that's the whole page bestie, go forth and certify 🌸 β€” this was version 3.5.6, dated 2026-04-07, from the CA.PL(1ossl) manual. periodt. πŸ’–

πŸ“¦ where this page comes from