EVP: Make the SIGNATURE implementation leaner
authorRichard Levitte <levitte@openssl.org>
Wed, 30 Oct 2019 15:59:34 +0000 (16:59 +0100)
committerRichard Levitte <levitte@openssl.org>
Tue, 5 Nov 2019 21:22:29 +0000 (22:22 +0100)
commit0e52100400e647aeb5b8ac1b92c74d53918d39a0
tree7775c86254a8c06b311950e9731d0ceecaeb262f
parentc0e0984f125ee30820520829c4c112b1e166f871
EVP: Make the SIGNATURE implementation leaner

Because the algorithm to use is decided already when creating an
EVP_PKEY_CTX regardless of how it was created, it turns out that it's
unnecessary to provide the SIGNATURE method explicitly, and rather
always have it be fetched implicitly.

This means fewer changes for applications that want to use new
signature algorithms / implementations.

Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/10303)
crypto/evp/evp_local.h
crypto/evp/m_sigver.c
crypto/evp/pmeth_fn.c
doc/man3/EVP_DigestSignInit.pod
doc/man3/EVP_PKEY_sign.pod
doc/man3/EVP_PKEY_verify.pod
doc/man3/EVP_PKEY_verify_recover.pod
include/openssl/evp.h
util/libcrypto.num