diff options
| author | Richard Levitte <levitte@openssl.org> | 2019-10-30 18:03:07 +0100 |
|---|---|---|
| committer | Richard Levitte <levitte@openssl.org> | 2019-11-05 22:20:06 +0100 |
| commit | c0e0984f125ee30820520829c4c112b1e166f871 (patch) | |
| tree | fbc23f98d35454a4b83bd08b11dea17acd0e8460 /util | |
| parent | 677c4a012a7e72b5f2dd239639034f01fad850bf (diff) | |
EVP: Make the KEYEXCH 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 KEYEXCH method explicitly, and rather
always have it be fetched implicitly.
This means fewer changes for applications that want to use new key
exchange algorithms / implementations.
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/10305)
Diffstat (limited to 'util')
| -rw-r--r-- | util/libcrypto.num | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/util/libcrypto.num b/util/libcrypto.num index 8a88b6e8bd..737a2aba98 100644 --- a/util/libcrypto.num +++ b/util/libcrypto.num @@ -4666,7 +4666,7 @@ BN_priv_rand_ex 4782 3_0_0 EXIST::FUNCTION: BN_rand_range_ex 4783 3_0_0 EXIST::FUNCTION: BN_priv_rand_range_ex 4784 3_0_0 EXIST::FUNCTION: BN_generate_prime_ex2 4785 3_0_0 EXIST::FUNCTION: -EVP_PKEY_derive_init_ex 4786 3_0_0 EXIST::FUNCTION: +EVP_PKEY_derive_init_ex 4786 3_0_0 NOEXIST::FUNCTION: EVP_KEYEXCH_free 4787 3_0_0 EXIST::FUNCTION: EVP_KEYEXCH_up_ref 4788 3_0_0 EXIST::FUNCTION: EVP_KEYEXCH_fetch 4789 3_0_0 EXIST::FUNCTION: |