PKCS12_CREATE(3ossl)

📦
version 3.5.9 · 8 versions
, in fedora 43, fedora 44

💖 PKCS12_CREATE 💖

okay bestie, sit down, hydrate, and let me tell you about PKCS12_CREATE(3ossl) — it's an OpenSSL thing and it's literally the whole vibe of making a PKCS#12 structure out of thin air. no cap. 🎀

✨ NAME ✨

PKCS12_create, PKCS12_create_ex, PKCS12_create_cb, PKCS12_create_ex2 — create a PKCS#12 structure 🦋

✨ SYNOPSIS ✨

#include <openssl/pkcs12.h>

PKCS12 *PKCS12_create(const char *pass, const char *name, EVP_PKEY *pkey,
                      X509 *cert, STACK_OF(X509) *ca,
                      int nid_key, int nid_cert, int iter, int mac_iter, int keytype);
PKCS12 *PKCS12_create_ex(const char *pass, const char *name, EVP_PKEY *pkey,
                         X509 *cert, STACK_OF(X509) *ca, int nid_key, int nid_cert,
                         int iter, int mac_iter, int keytype,
                         OSSL_LIB_CTX *ctx, const char *propq);

typedef int PKCS12_create_cb(PKCS12_SAFEBAG *bag, void *cbarg);

PKCS12 *PKCS12_create_ex2(const char *pass, const char *name, EVP_PKEY *pkey,
                          X509 *cert, STACK_OF(X509) *ca, int nid_key, int nid_cert,
                          int iter, int mac_iter, int keytype,
                          OSSL_LIB_CTX *ctx, const char *propq,
                          PKCS12_create_cb *cb, void *cbarg);
=head1 DESCRIPTION
not me pointing out that there's a =head1 DESCRIPTION chillin' at the bottom of that code block 💀 it's literally in the source, so it stays. we respect the lore.

🌸 DESCRIPTION 🌸

PKCS12_create() creates a PKCS#12 structure. that's it. that's the whole job. iconic behavior honestly. 👑

pass is the passphrase to use. name is the friendlyName to use for the supplied certificate and key. pkey is the private key to include in the structure, and cert its corresponding certificates. ca, if not NULL, is an optional set of certificates to also include in the structure. 🎀

nid_key and nid_cert are the encryption algorithms that should be used for the key and certificate respectively. The modes GCM, CCM, XTS, and OCB are unsupported. iter is the encryption algorithm iteration count to use and mac_iter is the MAC iteration count to use. keytype is the type of key.

PKCS12_create_ex() is literally identical to PKCS12_create() but it lets a library context ctx and property query propq be used to select algorithm implementations. glow-up. ✨

PKCS12_create_ex2() is identical to PKCS12_create_ex() but lets a user defined callback cb of type PKCS12_create_cb be specified, and also lets an optional argument cbarg be passed back to the callback. so much main character energy. 💅

The cb, if specified, will be called for every safebag added to the PKCS12 structure and allows for optional application processing on the associated safebag. for example, one such use could be to add attributes to the safebag. cute, right? 🫶

💅 NOTES 💅

The parameters nid_key, nid_cert, iter, mac_iter and keytype can all be set to zero and sensible defaults will be used. zero = "you decide, queen." 😌

These defaults are: AES password based encryption (PBES2 with PBKDF2 and AES-256-CBC) for private keys and certificates, the PBKDF2 and MAC key derivation iteration count of PKCS12_DEFAULT_ITER (currently 2048), and MAC algorithm HMAC with SHA2-256. The MAC key derivation algorithm used for the outer PKCS#12 structure is PKCS12KDF. 🌈

The default MAC iteration count is 1 in order to retain compatibility with old software which did not interpret MAC iteration counts. If such compatibility is not required then mac_iter should be set to PKCS12_DEFAULT_ITER. yes bestie, backwards compatibility is why we can't have nice things. 😭

keytype adds a flag to the store private key. This is a non standard extension that is only currently interpreted by MSIE. If set to zero the flag is omitted, if set to KEY_SIG the key can be used for signing only, if set to KEY_EX it can be used for signing and encryption. This option was useful for old export grade software which could use signing only keys of arbitrary size but had restrictions on the permissible sizes of keys which could be used for encryption. it's giving ancient artifact energy 🏺

If name is NULL and cert contains an alias then this will be used for the corresponding friendlyName in the PKCS12 structure instead. Similarly, if pkey is NULL and cert contains a keyid then this will be used for the corresponding localKeyID in the PKCS12 structure instead of the id calculated from the pkey. it's the fallback plan, and honestly? she's serving. ✨

For all certificates in ca then if a certificate contains an alias or keyid then this will be used for the corresponding friendlyName or localKeyID in the PKCS12 structure.

Either pkey, cert or both can be NULL to indicate that no key or certificate is required. In previous versions both had to be present or a fatal error is returned. glow-up of the century. 🔥

nid_key or nid_cert can be set to -1 indicating that no encryption should be used.

mac_iter can be set to -1 and the MAC will then be omitted entirely. This can be useful when running with the FIPS provider as the PKCS12KDF is not a FIPS approvable algorithm.

⚠️ PKCS12_create() makes assumptions regarding the encoding of the given pass phrase. See passphrase-encoding(7) for more information. bestie please read that one, it's not a drill. 🙈

If cb is specified, then it should return 1 for success and -1 for a fatal error. A return of 0 is intended to mean to not add the bag after all. three outcomes, three vibes, choose wisely. 💀

🎀 RETURN VALUES 🎀

PKCS12_create() returns a valid PKCS12 structure or NULL if an error occurred. that's it, that's the duality of woman. ✨

🌟 CONFORMING TO 🌟

IETF RFC 7292 (<https://tools.ietf.org/html/rfc7292>) — we stay standards compliant, periodt. 👑

🦋 SEE ALSO 🦋

go read your other besties too, iykyk 💜

💜 HISTORY 💜

PKCS12_create_ex() was added in OpenSSL 3.0. PKCS12_create_ex2() was added in OpenSSL 3.2.

The defaults for encryption algorithms, MAC algorithm, and the MAC key derivation iteration count were changed in OpenSSL 3.0 to more modern standards. she evolved. 💅

Copyright 2002-2024 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!! you literally ate this one. 🍓

and for the cute sign-off: this whole thing is from OpenSSL 3.5.9, dated 2026-09-29, and it's the PKCS12_CREATE(3ossl) page. mwah. 😘✨🫶

📦 where this page comes from