doc: note that these KDFs require the legacy provider to be available
authorPauli <pauli@openssl.org>
Sun, 26 Sep 2021 23:05:32 +0000 (09:05 +1000)
committerPauli <pauli@openssl.org>
Tue, 28 Sep 2021 08:08:42 +0000 (18:08 +1000)
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/15968)

doc/man7/EVP_KDF-PBKDF1.pod
doc/man7/EVP_KDF-PVKKDF.pod

index ae13765211de5d1dec58c507a2231b4d2c57ecce..0d24325cd9c6d2ba2531b4d4f4624b5194143e9f 100644 (file)
@@ -53,6 +53,8 @@ of candidate passwords.
 No assumption is made regarding the given password; it is simply treated as a
 byte sequence.
 
+The legacy provider needs to be available in order to access this algorithm.
+
 =head1 CONFORMING TO
 
 RFC 8018
@@ -64,7 +66,8 @@ L<EVP_KDF_CTX_new(3)>,
 L<EVP_KDF_CTX_free(3)>,
 L<EVP_KDF_CTX_set_params(3)>,
 L<EVP_KDF_derive(3)>,
-L<EVP_KDF(3)/PARAMETERS>
+L<EVP_KDF(3)/PARAMETERS>,
+L<OSSL_PROVIDER-legacy(7)>
 
 =head1 HISTORY
 
index 0d864d716953b9fecfad9da327c432baf51cbebc..08aff0c9e75a25fca1b26890346b5d2d1a545665 100644 (file)
@@ -43,6 +43,8 @@ encryption algorithm from a password in the "pass" and a salt in "salt".
 No assumption is made regarding the given password; it is simply treated as a
 byte sequence.
 
+The legacy provider needs to be available in order to access this algorithm.
+
 =head1 SEE ALSO
 
 L<EVP_KDF(3)>,
@@ -50,7 +52,8 @@ L<EVP_KDF_CTX_new(3)>,
 L<EVP_KDF_CTX_free(3)>,
 L<EVP_KDF_CTX_set_params(3)>,
 L<EVP_KDF_derive(3)>,
-L<EVP_KDF(3)/PARAMETERS>
+L<EVP_KDF(3)/PARAMETERS>,
+L<OSSL_PROVIDER-legacy(7)>
 
 =head1 HISTORY