From: Tomas Mraz <tomas@openssl.org>
Date: Fri, 20 Jan 2023 10:40:45 +0000 (+0100)
Subject: MD5.pod: Recommend SHA-2 or SHA-3 family hashes instead of legacy ones
X-Git-Tag: openssl-3.2.0-alpha1~1415
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=61222b95ff20f6a7bb20668e43b657561efdb922;p=thirdparty%2Fopenssl.git

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 81e220fe42a..535fb925a31 100644
--- 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