A proposal to expose more of OpenSSL's key derivation functions (KDFs) through Erlang's built-in `crypto` module. Currently only `pbkdf2_hmac/5` is available, but since libcrypto already links against OpenSSL's EVP_KDF, functions like scrypt, Argon2id, Concat KDF, and HKDF could be exposed without requiring a custom NIF. A unified `crypto:kdf/3` API is proposed, with algorithm-specific parameters passed as a map. Argon2 would require OpenSSL 3.2+, falling back to `notsup` on older versions. The post is an early-stage proposal seeking OTP team interest before a PR is opened.
38 Impressions