OPENSSL-CMS(1ossl)

📦 version 3.5.0, in opensuse-leap 16.0

💖 OPENSSL-CMS(1ossl) — CMS command 💖

okay bestie, this is the manual for openssl-cms, aka the CMS command. it handles CMS-format data and it's lowkey iconic. let's get into it 💅

🎀 NAME 🎀

openssl-cms — the CMS command. periodt.

✨ SYNOPSIS ✨

openssl cms [-help]

General options:

[-in filename] [-out filename] [-config configfile]

Operation options:

[-encrypt] [-decrypt] [-sign] [-verify] [-resign] [-sign_receipt]
[-verify_receipt receipt] [-digest digest] [-digest_create]
[-digest_verify] [-compress] [-uncompress] [-EncryptedData_encrypt]
[-EncryptedData_decrypt] [-data_create] [-data_out] [-cmsout]

File format options:

[-inform DER|PEM|SMIME] [-outform DER|PEM|SMIME] [-rctform DER|PEM|SMIME] [-stream] [-indef] [-noindef] [-binary] [-crlfeol] [-asciicrlf]

Keys and password options:

[-pwri_password password] [-secretkey key] [-secretkeyid id] [-inkey filename|uri] [-passin arg] [-keyopt name:parameter] [-keyform DER|PEM|P12|ENGINE] [-engine id] [-provider name] [-provider-path path] [-provparam [name:]key=value] [-propquery propq] [-rand files] [-writerand file]

Encryption options:

[-originator file] [-recip file] [recipient-cert ...]  [-cipher] [-wrap cipher] [-aes128-wrap] [-aes192-wrap] [-aes256-wrap] [-des3-wrap] [-debug_decrypt]

Signing options:

[-md digest] [-signer file] [-certfile file] [-cades] [-nodetach] [-nocerts] [-noattr] [-nosmimecap] [-no_signing_time] [-receipt_request_all] [-receipt_request_first] [-receipt_request_from emailaddress] [-receipt_request_to emailaddress]

Verification options:

[-signer file] [-content filename] [-no_content_verify] [-no_attr_verify] [-nosigs] [-noverify] [-nointern] [-cades] [-verify_retcode] [-CAfile file] [-no-CAfile] [-CApath dir] [-no-CApath] [-CAstore uri] [-no-CAstore]

Output options:

[-keyid] [-econtent_type type] [-text] [-certsout file] [-to addr] [-from addr] [-subject subj]

Printing options:

[-noout] [-print] [-nameopt option] [-receipt_request_print]

Validation options:

[-allow_proxy_certs] [-attime timestamp] [-no_check_time] [-check_ss_sig] [-crl_check] [-crl_check_all] [-explicit_policy] [-extended_crl] [-ignore_critical] [-inhibit_any] [-inhibit_map] [-partial_chain] [-policy arg] [-policy_check] [-policy_print] [-purpose purpose] [-suiteB_128] [-suiteB_128_only] [-suiteB_192] [-trusted_first] [-no_alt_chains] [-use_deltas] [-auth_level num] [-verify_depth num] [-verify_email email] [-verify_hostname hostname] [-verify_ip ip] [-verify_name name] [-x509_strict] [-issuer_checks]

🦋 DESCRIPTION 🦋

okay so this command handles data in CMS format — think S/MIME v3.1 email messages, bestie. It can encrypt, decrypt, sign, verify, compress, uncompress, and print messages. the range? iconic. 💅

👑 OPTIONS 👑

There are a number of operation options that set the type of operation to be performed: encrypt, decrypt, sign, verify, resign, sign_receipt, verify_receipt, digest_create, digest_verify, compress, uncompress, EncryptedData_encrypt, EncryptedData_decrypt, data_create, data_out, or cmsout. The relevance of the other options depends on the operation type, and their meaning may vary according to it.

  • -help — print out a usage message.

🌸 General options 🌸

  • -in filename — the input message to be encrypted or signed, or the message to be decrypted or verified.
  • -out filename — the message text that has been decrypted or verified, or the output MIME format message that has been signed or verified.
  • -config configfile — see "Configuration Option" in openssl(1).

🔥 Operation options 🔥

  • -encrypt — encrypt data for the given recipient certificates. The input file is the message to be encrypted. The output file is the encrypted data in MIME format. The actual CMS type is EnvelopedData.
heads up: no revocation check is done for the recipient cert, so if that key has been compromised, others may be able to decrypt the text. 😭
  • -decrypt — decrypt data using the supplied certificate and private key. Expects encrypted data in MIME format for the input file. The decrypted data is written to the output file.
  • -sign — sign data using the supplied certificate and private key. Input file is the message to be signed. The signed data in MIME format is written to the output file.
  • -verify — verify signed data. Expects signed data on input and outputs the signed data. Both clear text and opaque signing are supported.

By default, validation of signer certificates and their chain is done w.r.t. the S/MIME signing (smimesign) purpose. For details see "Certificate Extensions" in openssl-verification-options(1).

  • -resign — resign a message: take an existing message and one or more new signers.
  • -sign_receipt — generate and output a signed receipt for the supplied message. The input message must contain a signed receipt request. Functionality is otherwise similar to the -sign operation.
  • -verify_receipt receipt — verify a signed receipt in filename receipt. The input message must contain the original receipt request. Functionality is otherwise similar to the -verify operation.
  • -digest digest — when used with -sign, provides the digest in hexadecimal form instead of computing it from the original message content. Cannot be combined with -in or -nodetach.

This operation is the CMS equivalent of openssl-pkeyutl(1) signing. When signing a pre-computed digest, the security relies on the digest and its computation from the original message being trusted.

  • -digest_create — create a CMS DigestedData type.
  • -digest_verify — verify a CMS DigestedData type and output the content.
  • -compress — create a CMS CompressedData type. OpenSSL must be compiled with zlib support for this option to work, otherwise it will output an error.
  • -uncompress — uncompress a CMS CompressedData type and output the content. OpenSSL must be compiled with zlib support for this option to work, otherwise it will output an error.
  • -EncryptedData_encrypt — encrypt content using supplied symmetric key and algorithm using a CMS EncryptedData type and output the content.
  • -EncryptedData_decrypt — decrypt content using supplied symmetric key and algorithm using a CMS EncryptedData type and output the content.
  • -data_create — create a CMS Data type.
  • -data_out — Data type and output the content.
  • -cmsout — takes an input message and writes out a PEM encoded CMS structure.

🎀 File format options 🎀

  • -inform DER|PEM|SMIME — the input format of the CMS structure (if one is being read); the default is SMIME. See openssl-format-options(1) for details.
  • -outform DER|PEM|SMIME — the output format of the CMS structure (if one is being written); the default is SMIME. See openssl-format-options(1) for details.
  • -rctform DER|PEM|SMIME — the signed receipt format for use with the -receipt_verify; the default is SMIME. See openssl-format-options(1) for details.
  • -stream, -indef — these options are equivalent and enable streaming I/O for encoding operations. This permits single pass processing of data without the need to hold the entire contents in memory, potentially supporting very large files. Streaming is automatically set for S/MIME signing with detached data if the output format is SMIME; it is currently off by default for all other operations.
  • -noindef — disable streaming I/O where it would produce an indefinite length constructed encoding. This option currently has no effect. In future, streaming will be enabled by default on all relevant operations and this option will disable it.
  • -binary — normally the input message is converted to "canonical" format which is effectively using CR and LF as end of line: as required by the S/MIME specification. When this option is present, no translation occurs. This is useful when handling binary data which may not be in MIME format.
  • -crlfeol — normally the output file uses a single LF as end of line. When this option is present, CRLF is used instead.
  • -asciicrlf — when signing, use ASCII CRLF format canonicalisation. This strips trailing whitespace from all lines, deletes trailing blank lines at EOF, and sets the encapsulated content type. This option is normally used with detached content and an output signature format of DER. This option is not normally needed when verifying, as it is enabled automatically if the encapsulated content format is detected.

💜 Keys and password options 💜

  • -pwri_password password — specify password for recipient.
  • -secretkey key — specify symmetric key to use. The key must be supplied in hex format and be consistent with the algorithm used. Supported by the -EncryptedData_encrypt, -EncryptedData_decrypt, -encrypt, and -decrypt options. When used with -encrypt or -decrypt, the supplied key is used to wrap or unwrap the content encryption key using an AES key in the KEKRecipientInfo type.
  • -secretkeyid id — the key identifier for the supplied symmetric key for KEKRecipientInfo type. This option must be present if the -secretkey option is used with -encrypt. With -decrypt operations, the id is used to locate the relevant key; if it is not supplied, then an attempt is made to decrypt any KEKRecipientInfo structures.
  • -inkey filename|uri — the private key to use when signing or decrypting. This must match the corresponding certificate. If this option is not specified, then the private key must be included in the certificate file specified with the -recip or -signer file. When signing, this option can be used multiple times to specify successive keys.
  • -passin arg — the private key password source. For more information about the format of arg, see openssl-passphrase-options(1).
  • -keyopt name:parameter — for signing and encryption, this option can be used multiple times to set customised parameters for the preceding key or certificate. It can currently be used to set RSA-PSS for signing, RSA-OAEP for encryption, or to modify default parameters for ECDH.
  • -keyform DER|PEM|P12|ENGINE — the format of the private key file; unspecified by default. See openssl-format-options(1) for details.
  • -engine id — see "Engine Options" in openssl(1). This option is deprecated.
deprecated, bestie — -engine is deprecated. 🫶

💌 Encryption and decryption options

  • -originator file — hands you the certificate of whoever originated the encrypted message ✨. You need this for decryption when Key Agreement is being used for a shared key. Currently it's not allowed for encryption, so don't try it bestie 💅
  • -recip file — okay so it does different things depending on which way you're going:
    • When you're decrypting a message, this specifies the certificate of the recipient. The certificate has to match one of the recipients of the message, no cap 🔥
    • When you're encrypting a message, this option can be used multiple times to specify each recipient. You must use this form if customised parameters are required (like, for example, to specify RSA-OAEP) 🎀
    • Only certificates carrying RSA, Diffie-Hellman or EC keys are supported by this option 🌸
  • recipient-cert ... — this is the alt route to -recip when encrypting 💖. One or more certificate filenames may be given.
  • -cipher — the encryption algorithm to use. Like, AES (256 bits) is -aes256, or triple DES (168 bits) is -des3 🦋. Any standard algorithm name (as used by the EVP_get_cipherbyname() function) can also be used, just put a dash in front, for example -aes-128-cbc. Peep openssl-enc(1) for a list of ciphers supported by your version of OpenSSL 👑
    • Currently, the AES variants with GCM mode are the only supported AEAD algorithms.
    • If you don't specify one, AES-256-CBC is the default ⭐
    • Only used with -encrypt and -EncryptedData_create commands.
  • -wrap cipher — cipher algorithm to use for key wrap when encrypting the message using Key Agreement for key transport 🎀. The algorithm you pick should be suitable for key wrap, mkay?
  • -aes128-wrap, -aes192-wrap, -aes256-wrap, -des3-wrap — use AES128, AES192, AES256, or 3DES-EDE, respectively, to wrap the key 💜. Depending on the OpenSSL build options used, -des3-wrap may not be supported 😭
  • -debug_decrypt — this one sets the CMS_DEBUG_DECRYPT flag. Use it with caution: see the notes section below, bestie ⚠️

✍️ Signing options

  • -md digest — digest algorithm to use when signing or resigning ✨. If it's not present then the default digest algorithm for the signing key gets used (usually SHA1).
  • -signer file — a signing certificate 🎀. When you're signing or resigning a message, this option can be used multiple times if you need more than one signer 💅
  • -certfile file — lets you specify additional certificates 🌸. When signing, these get included with the message. When verifying, these get searched for signer certificates and get used for chain building.
    • The input can be in PEM, DER, or PKCS#12 format.
  • -cades — when used with -sign, add an ESS signingCertificate or ESS signingCertificateV2 signed-attribute to the SignerInfo, so the signature complies with the requirements for a CAdES Basic Electronic Signature (CAdES-BES) 👑
  • -nodetach — when signing a message, use opaque signing 🦋: this form is more resistant to translation by mail relays, but it cannot be read by mail agents that don't support S/MIME. Without this option, cleartext signing with the MIME type multipart/signed is used.
  • -nocerts — when signing a message the signer's certificate is normally included; with this option it gets excluded 🙈. This reduces the size of the signed message, but the verifier must have a copy of the signer's certificate available locally (passed using the -certfile option, for example).
  • -noattr — normally when a message is signed a set of attributes gets included, which include the signing time and supported symmetric algorithms 💫. With this option they are not included.
  • -nosmimecap — exclude the list of supported algorithms from signed attributes; other options such as content type and (optionally) signing time are still included 💜
  • -no_signing_time — exclude the signing time from signed attributes; other options such as content type are still included ⭐
  • -receipt_request_all, -receipt_request_first — for the -sign option, include a signed receipt request 🎀. Indicate requests should be provided by all recipients, or first tier recipients (those mailed directly and not from a mailing list). Ignored if -receipt_request_from is included.
  • -receipt_request_from emailaddress — for the -sign option, include a signed receipt request 💌. Add an explicit email address where receipts should be supplied.
  • -receipt_request_to emailaddress — add an explicit email address where signed receipts should be sent to 📬. This option must be supplied if a signed receipt is requested.

🔍 Verification options

  • -signer file — if a message has been verified successfully, then the signer's certificate(s) get written to this file 💖 (assuming the verification was successful, obviously).
  • -content filename — this specifies a file containing the detached content for operations taking S/MIME input, like the -verify command 🌸. Only usable if the CMS structure is using the detached signature form where the content is not included. This option overrides any content if the input format is S/MIME and it uses the multipart/signed MIME content type 👑
  • -no_content_verify — do not verify signed content signatures 🙅‍♀️
  • -no_attr_verify — do not verify signed attribute signatures 🙅‍♀️
  • -nosigs — don't verify message signature, periodt 💅
  • -noverify — do not verify the signer's certificate of a signed message.
  • -nointern — when verifying a message, normally certificates (if any) included in the message are searched for the signing certificate 🦋. With this option, only the certificates specified in the -certfile option are used. The supplied certificates can still be used as untrusted CAs though, so no stress ✨
  • -cades — when used with -verify, require and check signer certificate digest 🔥. See the NOTES section for more details.
  • -verify_retcode — exit nonzero on verification failure 💀
  • -CAfile file, -no-CAfile, -CApath dir, -no-CApath, -CAstore uri, -no-CAstore — see "Trusted Certificate Options" in openssl-verification-options(1) for the deets 📖

📤 Output options

  • -keyid — use subject key identifier to identify certificates instead of issuer name and serial number 🔑. The supplied certificate must include a subject key identifier extension. Supported by -sign and -encrypt options.
  • -econtent_type type — set the encapsulated content type to type 🎀; if it's not supplied, the Data type is used. The type argument can be any valid OID name in either text or numerical format.
  • -text — this option adds plain text (text/plain) MIME headers to the supplied message if you're encrypting or signing ✨. If you're decrypting or verifying it strips off text headers: if the decrypted or verified message is not of MIME type text/plain then an error occurs 😭
  • -certsout file — any certificates contained in the input message get written to file 📁
  • -to, -from, -subject — the relevant email headers 💌. These are included outside the signed portion of a message so they may be included manually. If you're signing, then many S/MIME mail clients check the signer certificate's email address matches that specified in the From: address 👀

🖨️ Printing options

  • -noout — for the -cmsout operation, do not output the parsed CMS structure 🙈. This is useful if the syntax of the CMS structure is being checked.
  • -print — for the -cmsout operation, print out all fields of the CMS structure 🎀. This implies -noout. Mainly useful for testing purposes.
  • -nameopt option — for the -cmsout operation when the -print option is in use, specifies printing options for string fields ✨. For most cases utf8 is a reasonable value. See openssl-namedisplay-options(1) for details.
  • -receipt_request_print — for the -verify operation, print out the contents of any signed receipt requests 🧾

✅ Validation options

  • -allow_proxy_certs, -attime, -no_check_time, -check_ss_sig, -crl_check, -crl_check_all, -explicit_policy, -extended_crl, -ignore_critical, -inhibit_any, -inhibit_map, -no_alt_chains, -partial_chain, -policy, -policy_check, -policy_print, -purpose, -suiteB_128, -suiteB_128_only, -suiteB_192, -trusted_first, -use_deltas, -auth_level, -verify_depth, -verify_email, -verify_hostname, -verify_ip, -verify_name, -x509_strict, -issuer_checks — set various options of certificate chain verification 🛡️. See "Verification Options" in openssl-verification-options(1) for details.
Heads up bestie: any validation errors cause the command to exit 🚪💨

📝 NOTES 📝

ok so listen bestie, the MIME message has to be sent with no blank lines between the headers and the output. some mail programs will just auto-add a blank line on you (rude!), and piping the mail straight into sendmail is one way to get the correct format. slay.

the message you're signing or encrypting must include the necessary MIME headers, or a whole bunch of S/MIME clients won't display it properly (like, if at all 😭). you can use the -text option to automatically add plain text headers.

a "signed and encrypted" message is one where a signed message gets encrypted after. you make one by encrypting an already-signed message — check the examples section for the tea ☕

this version of the program only allows one signer per message, but it will verify multiple signers on received messages. some S/MIME clients literally choke if a message contains multiple signers. you can sign messages "in parallel" by signing an already signed message, iykyk.

the options -encrypt and -decrypt reflect common usage in S/MIME clients. strictly speaking these process CMS enveloped data: CMS encrypted data is used for other purposes.

the -resign option uses an existing message digest when adding a new signer. that means attributes must be present in at least one existing signer using the same message digest, or this operation will fail. no cap.

the -stream and -indef options enable streaming I/O support. as a result the encoding is BER using indefinite length constructed encoding and no longer DER. streaming is supported for the -encrypt operation and the -sign operation if the content is not detached.

streaming is always used for the -sign operation with detached data, but since the content is no longer part of the CMS structure the encoding remains DER.

🚨 okay this one's important: if you use -decrypt without a recipient certificate, an attempt is made to locate the recipient by trying each potential recipient in turn using the supplied private key. to thwart the MMA attack (Bleichenbacher's attack on PKCS #1 v1.5 RSA padding) all recipients are tried whether they succeed or not, and if no recipients match the message is "decrypted" using a random key which will typically output garbage 💀. the -debug_decrypt option can be used to disable the MMA attack protection and return an error if no recipient can be found: this option should be used with caution. for a fuller description see CMS_decrypt(3).

🎀 CADES BASIC ELECTRONIC SIGNATURE (CADES-BES) 🎀

a CAdES Basic Electronic Signature (CAdES-BES), as defined in the European Standard ETSI EN 319 122-1 V1.1.1, contains:

  • the signed user data as defined in CMS (RFC 3852);
  • content-type of the EncapsulatedContentInfo value being signed;
  • message-digest of the eContent OCTET STRING within encapContentInfo being signed;
  • an ESS signingCertificate or ESS signingCertificateV2 attribute, as defined in Enhanced Security Services (ESS), RFC 2634 and RFC 5035. an ESS signingCertificate attribute only allows for SHA-1 as digest algorithm. an ESS signingCertificateV2 attribute allows for any digest algorithm.
  • the digital signature value computed on the user data and, when present, on the signed attributes.
⚠️ NOTE that the -cades option applies to the -sign or -verify operations. with this option, the -verify operation also requires that the signingCertificate attribute is present and checks that the given identifiers match the verification trust chain built during the verification process.

🚪 EXIT CODES 🚪

  • 0 — the operation was completely successfully. (yes, that's the original wording, and honestly? iconic.)
  • 1 — an error occurred parsing the command options.
  • 2 — one of the input files could not be read.
  • 3 — an error occurred creating the CMS file or when reading the MIME message.
  • 4 — an error occurred decrypting or verifying the message.
  • 5 — the message was verified correctly but an error occurred writing out the signers certificates.

🦋 COMPATIBILITY WITH PKCS#7 FORMAT 🦋

openssl-smime(1) can only process the older PKCS#7 format. openssl cms supports Cryptographic Message Syntax format. use of some features will result in messages which cannot be processed by applications which only support the older format. these are detailed below 👇

  • the use of the -keyid option with -sign or -encrypt.
  • the -outform PEM option uses different headers.
  • the -compress option.
  • the -secretkey option when used with -encrypt.
  • the use of PSS with -sign.
  • the use of OAEP or non-RSA keys with -encrypt.

additionally the -EncryptedData_create and -data_create type cannot be processed by the older openssl-smime(1) command. rip to the old format honestly 💀

✨ EXAMPLES ✨

create a cleartext signed message:

openssl cms -sign -in message.txt -text -out mail.msg \
       -signer mycert.pem

create an opaque signed message:

openssl cms -sign -in message.txt -text -out mail.msg -nodetach \
       -signer mycert.pem

create a signed message, include some additional certificates and read the private key from another file:

openssl cms -sign -in in.txt -text -out mail.msg \
       -signer mycert.pem -inkey mykey.pem -certfile mycerts.pem

create a signed message with two signers, use key identifier:

openssl cms -sign -in message.txt -text -out mail.msg \
       -signer mycert.pem -signer othercert.pem -keyid

send a signed message under Unix directly to sendmail, including headers:

openssl cms -sign -in in.txt -text -signer mycert.pem \
       -from steve@openssl.org -to someone@somewhere \
       -subject "Signed message" | sendmail someone@somewhere

verify a message and extract the signer's certificate if successful:

openssl cms -verify -in mail.msg -signer user.pem -out signedtext.txt

send encrypted mail using triple DES:

openssl cms -encrypt -in in.txt -from steve@openssl.org \
       -to someone@somewhere -subject "Encrypted message" \
       -des3 user.pem -out mail.msg

sign and encrypt mail:

openssl cms -sign -in ml.txt -signer my.pem -text \
       | openssl cms -encrypt -out mail.msg \
       -from steve@openssl.org -to someone@somewhere \
       -subject "Signed and Encrypted message" -des3 user.pem
💡 note: the encryption command does not include the -text option because the message being encrypted already has MIME headers. don't add it twice bestie, we're not doing that.

decrypt a message:

openssl cms -decrypt -in mail.msg -recip mycert.pem -inkey key.pem

the output from Netscape form signing is a PKCS#7 structure with the detached signature format. you can use this program to verify the signature by line wrapping the base64 encoded structure and surrounding it with:

-----BEGIN PKCS7-----
-----END PKCS7-----

and using the command,

openssl cms -verify -inform PEM -in signature.pem -content content.txt

alternatively you can base64 decode the signature and use

openssl cms -verify -inform DER -in signature.der -content content.txt

create an encrypted message using 128 bit Camellia:

openssl cms -encrypt -in plain.txt -camellia128 -out mail.msg cert.pem

add a signer to an existing message:

openssl cms -resign -in mail.msg -signer newsign.pem -out mail2.msg

sign a message using RSA-PSS:

openssl cms -sign -in message.txt -text -out mail.msg \
       -signer mycert.pem -keyopt rsa_padding_mode:pss

create an encrypted message using RSA-OAEP:

openssl cms -encrypt -in plain.txt -out mail.msg \
       -recip cert.pem -keyopt rsa_padding_mode:oaep

use SHA256 KDF with an ECDH certificate:

openssl cms -encrypt -in plain.txt -out mail.msg \
       -recip ecdhcert.pem -keyopt ecdh_kdf_md:sha256

print CMS signed binary data in human-readable form:

openssl cms -in signed.cms -binary -inform DER -cmsout -print

💀 BUGS 💀

ngl, there are some things to know:

  • the MIME parser isn't very clever: it seems to handle most messages that I've thrown at it but it may choke on others.
  • the code currently will only write out the signer's certificate to a file: if the signer has a separate encryption certificate this must be manually extracted. there should be some heuristic that determines the correct encryption certificate.
  • ideally a database should be maintained of a certificates for each email address.
  • the code doesn't currently take note of the permitted symmetric encryption algorithms as supplied in the SMIMECapabilities signed attribute. this means the user has to manually include the correct encryption algorithm. it should store the list of permitted ciphers in a database and only use those.
  • no revocation checking is done on the signer's certificate.

👀 SEE ALSO 👀

ossl_store-file(7)

🕰️ HISTORY 🕰️

the default encryption cipher was changed from 3DES to AES-256 in OpenSSL 3.5.

the use of multiple -signer options and the -resign command were first added in OpenSSL 1.0.0.

the -keyopt option was added in OpenSSL 1.0.2.

support for RSA-OAEP and RSA-PSS was added in OpenSSL 1.0.2.

the use of non-RSA keys with -encrypt and -decrypt was added in OpenSSL 1.0.2.

the -no_alt_chains option was added in OpenSSL 1.0.2b.

the -nameopt option was added in OpenSSL 3.0.0.

the -engine option was deprecated in OpenSSL 3.0.

the -digest option was added in OpenSSL 3.2.

Copyright 2008-2025 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>.

and that's the whole page bestie!! 💅✨ this lil masterpiece is from the OpenSSL fam, version 3.5.0, dated 2026-09-25 — go forth and CMS responsibly 🫶🎀

📦 where this page comes from