[openssl-commits] [openssl] master update

[paul.dale at oracle.com]

The branch master has been updated
       via  79b49fb00d61f8bc41fe20694da26a18ddfd3b02 (commit)
      from  a9dd51a800f1920aa7545dc2f4f831000a60af48 (commit)


- Log -----------------------------------------------------------------
commit 79b49fb00d61f8bc41fe20694da26a18ddfd3b02
Author: Pauli <paul.dale at oracle.com>
Date:   Tue Mar 20 10:03:10 2018 +1000

    Remove mention of link between message digests and public key algorithms.
    
    The comment in EVP_DigestInit.pod is:
    
    > Returns the NID of the public key signing algorithm associated with this
    digest. For example EVP_sha1() is associated with RSA so this will return
    B<NID_sha1WithRSAEncryption>. Since digests and signature algorithms are no
    longer linked this function is only retained for compatibility reasons.
    
    
    I.e. there is no link anymore.
    
    Reviewed-by: Rich Salz <rsalz at openssl.org>
    (Merged from https://github.com/openssl/openssl/pull/5682)

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

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

diff --git a/doc/man3/EVP_SignInit.pod b/doc/man3/EVP_SignInit.pod
index 987526c..c171b4c 100644
--- a/doc/man3/EVP_SignInit.pod
+++ b/doc/man3/EVP_SignInit.pod
@@ -66,11 +66,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/man3/EVP_VerifyInit.pod b/doc/man3/EVP_VerifyInit.pod
index ad8a8c0..f0d734c 100644
--- a/doc/man3/EVP_VerifyInit.pod
+++ b/doc/man3/EVP_VerifyInit.pod
@@ -52,11 +52,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.