From: Dmitry Belyavskiy <beldmit@gmail.com>
Date: Tue, 22 Jun 2021 15:33:12 +0000 (+0200)
Subject: Some clear guidelines for the legacy algs.
X-Git-Tag: openssl-3.0.0-beta2~229
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=13757e128378af79b3522002b4ae6b2a0678cf96;p=thirdparty%2Fopenssl.git

Some clear guidelines for the legacy algs.

Reviewed-by: Tomas Mraz <tomas@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/15860)
---

diff --git a/doc/man7/migration_guide.pod b/doc/man7/migration_guide.pod
index 82c7ffcc432..6d281472c97 100644
--- a/doc/man7/migration_guide.pod
+++ b/doc/man7/migration_guide.pod
@@ -60,6 +60,12 @@ There is however a dedicated C<install_fips> make target, which serves the
 special purpose of installing only the FIPS provider into an existing
 OpenSSL installation.
 
+Not all algorithms may be available for the application at a particular moment.
+If the application code uses any digest or cipher algorithm via the EVP interface,
+the application should verify the result of the L<EVP_EncryptInit(3)>,
+L<EVP_EncryptInit_ex(3)>, and L<EVP_DigestInit(3)> functions. In case when
+the requested algorithm is not available, these functions will fail.
+
 See also L</Legacy Algorithms> for information on the legacy provider.
 
 See also L</Completing the installation of the FIPS Module> and