EVP_KDF-PKCS12KDF(7SSL)

📦
version 4.0.3 · 13 versions
, in ubuntu stonking

💖 EVP_KDF-PKCS12KDF — the PKCS#12 EVP_KDF implementation 💖

okay bestie, this is the manual page for EVP_KDF-PKCS12KDF from the OpenSSL crew, and it's genuinely so much less scary than the name makes it look. let's get into it ✨

🌸 NAME 🌸

EVP_KDF-PKCS12KDF — the PKCS#12 EVP_KDF implementation. that's it, that's the whole name, she's concise 💅

🦋 DESCRIPTION 🦋

so this is the page for computing the PKCS#12 password-based KDF through the EVP_KDF API. yes, KDF = key derivation function, iykyk.

The EVP_KDF-PKCS12KDF algorithm implements the PKCS#12 password-based key derivation function, exactly as described in appendix B of RFC 7292 (PKCS #12: Personal Information Exchange Syntax). it derives a key from a password using a salt, iteration count and the intended usage. cute, right? 🎀

✨ Identity ✨

"PKCS12KDF" is the name for this implementation. that's the magic string, bestie — you can use it with the EVP_KDF_fetch() function. periodt.

🫶 Supported parameters 🫶

here's the menu of things you can hand her. the supported parameters are:

  • "pass" (OSSL_KDF_PARAM_PASSWORD) — <octet string> 💧
  • "salt" (OSSL_KDF_PARAM_SALT) — <octet string> 🧂
  • "iter" (OSSL_KDF_PARAM_ITER) — <unsigned integer> 🔁
  • "properties" (OSSL_KDF_PARAM_PROPERTIES) — <UTF8 string>
  • "digest" (OSSL_KDF_PARAM_DIGEST) — <UTF8 string>

These parameters work as described in "PARAMETERS" in EVP_KDF(3). no cap, go read that one too.

  • "id" (OSSL_KDF_PARAM_PKCS12_ID) — <integer>. This parameter is used to specify the intended usage of the output bits, as per RFC 7292 section B.3. it's giving "what is this key even for" energy and honestly we respect it.

👑 NOTES 👑

⚠️ heads up bestie: this algorithm is not available in the FIPS provider as it is not FIPS approvable. so if you're in FIPS land, this one's not coming to the party. 💀

A typical application of this algorithm is to derive keying material for an encryption algorithm from a password in "pass", a salt in "salt", and an iteration count. classic trio, they ate.

Increasing the "iter" parameter slows down the algorithm, which makes it harder for an attacker to perform a brute force attack using a large number of candidate passwords. so yes, more iterations = more patience required = more safety. iconic tradeoff honestly 🌈

No assumption is made regarding the given password; it is simply treated as a byte sequence. no vibe check, no judgment, no UTF-8 drama — just bytes. main character energy fr fr.

⭐ CONFORMING TO ⭐

RFC7292

she conforms, she's certified, she's that girl ✨

💜 SEE ALSO 💜

go click around, bestie, it's a whole web of lore 🕸️

🎀 HISTORY 🎀

This functionality was added in OpenSSL 3.0. so she's a 3.0 girlie and she's been thriving ever since 🦋

Copyright 2020-2023 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!! this was EVP_KDF-PKCS12KDF(7SSL) from OpenSSL, version 4.0.3, dated 2026-09-29. mwah, love u, go derive some keys responsibly 💖💅✨

📦 where this page comes from