EVP_KDF-PBKDF1(7ossl)
π EVP_KDF-PBKDF1 β the PBKDF1 glow-up, explained
okay so bestie, welcome to the EVP_KDF-PBKDF1 page from the OpenSSL 7ossl manual β no cap, this is the whole thing, just with better vibes. π
β¨ NAME β¨
EVP_KDF-PBKDF1 β literally the PBKDF1 EVP_KDF implementation, that's her, that's the whole name π«Ά
πΈ DESCRIPTION πΈ
So this page is all about support for computing the PBKDF1 password-based KDF through the EVP_KDF API. Slay.
The EVP_KDF-PBKDF1 algorithm implements the PBKDF1 password-based key derivation function, as described in RFC 8018; it derives a key from a password using a salt and iteration count. Iconic behaviour, honestly. π₯
π Identity π
"PBKDF1" is the name for this implementation β that's her government name, iykyk β and it can be used with the EVP_KDF_fetch() function. π
π¦ Supported parameters π¦
The supported parameters are, in order, bestie:
"pass"(OSSL_KDF_PARAM_PASSWORD) <octet string> β the password, as an octet string."salt"(OSSL_KDF_PARAM_SALT) <octet string> β the salt, also an octet string."iter"(OSSL_KDF_PARAM_ITER) <unsigned integer> β the iteration count. This parameter has a default value of0and should be set. Not me leaving it at0, please set it. π"properties"(OSSL_KDF_PARAM_PROPERTIES) <UTF8 string> β works as described in"PARAMETERS"inEVP_KDF(3)."digest"(OSSL_KDF_PARAM_DIGEST) <UTF8 string> β also works as described in"PARAMETERS"inEVP_KDF(3).
β NOTES β
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 combo, honestly. π§
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 likeβ¦ more iterations = more main character energy for your security, less for the attackers. π
No assumption is made regarding the given password; it is simply treated as a byte sequence. She's not judging your password, she's just reading bytes. π
π¨ Heads up bestie: the legacy provider needs to be available in order to access this algorithm. No legacy provider, no PBKDF1. Periodt.
π CONFORMING TO π
RFC 8018 β that's the standard, and she ate. π
π SEE ALSO π
EVP_KDF(3)EVP_KDF_CTX_new(3)EVP_KDF_CTX_free(3)EVP_KDF_CTX_set_params(3)EVP_KDF_derive(3)"PARAMETERS"inEVP_KDF(3)OSSL_PROVIDER-legacy(7)
π°οΈ HISTORY π°οΈ
This functionality was added in OpenSSL 3.0. She's been iconic since day one. β
π COPYRIGHT π
Copyright 2021 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, nothing skipped, bestie π«Ά β this was OpenSSL 3.5.9, dated 2026-09-29, signing off from the EVP_KDF-PBKDF1(7ossl) manual. mwah ππ
π¦ where this page comes from
- alpine 3.23: openssl-doc 3.5.9-r0 Β· Apache-2.0
- alpine 3.24: openssl-doc 3.5.9-r0 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms