MD5.pod: Recommend SHA-2 or SHA-3 family hashes instead of legacy ones

Reviewed-by: Matthias St. Pierre <Matthias.St.Pierre@ncp-e.com>
Reviewed-by: Hugo Landau <hlandau@openssl.org>
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/20095)

diff --git a/doc/man3/MD5.pod b/doc/man3/MD5.pod
index 81e220fe42aa5af6e9909d0028b01f3df6be0fd8..535fb925a312c5845bf17263d73b4a16cca8b7c5 100644 (file)
--- a/doc/man3/MD5.pod
+++ b/doc/man3/MD5.pod
@@ -80,8 +80,8 @@ etc. instead of calling the hash functions directly.
 =head1 NOTE
 
 MD2, MD4, and MD5 are recommended only for compatibility with existing
-applications. In new applications, SHA-1 or RIPEMD-160 should be
-preferred.
+applications. In new applications, hashes from the SHA-2 or SHA-3 family
+should be preferred.
 
 =head1 RETURN VALUES
 
@@ -97,7 +97,7 @@ RFC 1319, RFC 1320, RFC 1321
 
 =head1 SEE ALSO
 
-L<EVP_DigestInit(3)>
+L<EVP_DigestInit(3)>, L<EVP_MD-SHA2(7)>, L<EVP_MD-SHA3(7)>
 
 =head1 HISTORY