[openssl-commits] [openssl] OpenSSL_1_1_0-stable update

[paul.dale at oracle.com]

The branch OpenSSL_1_1_0-stable has been updated
       via  b9b5e7144af84dd9b66d31ed6d009b40c5bcd514 (commit)
      from  418c784b114a37fe948517ea0a257bea905b3c37 (commit)


- Log -----------------------------------------------------------------
commit b9b5e7144af84dd9b66d31ed6d009b40c5bcd514
Author: Pauli <paul.dale at oracle.com>
Date:   Tue Mar 20 11:09:38 2018 +1000

    Remove mentioned link between message digests and public key algorithms.
    
    Refer #5682 This is the same but for 1.1.0
    
    Reviewed-by: Rich Salz <rsalz at openssl.org>
    (Merged from https://github.com/openssl/openssl/pull/5683)

-----------------------------------------------------------------------

Summary of changes:
 doc/crypto/EVP_SignInit.pod   | 5 -----
 doc/crypto/EVP_VerifyInit.pod | 5 -----
 2 files changed, 10 deletions(-)

diff --git a/doc/crypto/EVP_SignInit.pod b/doc/crypto/EVP_SignInit.pod
index c40da1e..9279ce7 100644
--- a/doc/crypto/EVP_SignInit.pod
+++ b/doc/crypto/EVP_SignInit.pod
@@ -59,11 +59,6 @@ The B<EVP> interface to digital signatures should almost always be used in
 preference to the low level interfaces. This is because the code then becomes
 transparent to the algorithm used and much more flexible.
 
-Due to the link between message digests and public key algorithms the correct
-digest algorithm must be used with the correct public key type. A list of
-algorithms and associated public key algorithms appears in
-L<EVP_DigestInit(3)>.
-
 When signing with DSA private keys the random number generator must be seeded
 or the operation will fail. The random number generator does not need to be
 seeded for RSA signatures.
diff --git a/doc/crypto/EVP_VerifyInit.pod b/doc/crypto/EVP_VerifyInit.pod
index ffb6f14..ee1578a 100644
--- a/doc/crypto/EVP_VerifyInit.pod
+++ b/doc/crypto/EVP_VerifyInit.pod
@@ -51,11 +51,6 @@ The B<EVP> interface to digital signatures should almost always be used in
 preference to the low level interfaces. This is because the code then becomes
 transparent to the algorithm used and much more flexible.
 
-Due to the link between message digests and public key algorithms the correct
-digest algorithm must be used with the correct public key type. A list of
-algorithms and associated public key algorithms appears in
-L<EVP_DigestInit(3)>.
-
 The call to EVP_VerifyFinal() internally finalizes a copy of the digest context.
 This means that calls to EVP_VerifyUpdate() and EVP_VerifyFinal() can be called
 later to digest and verify additional data.