diff options
| author | jwalch <jeremy.walch@gmail.com> | 2020-09-24 11:43:06 -0400 |
|---|---|---|
| committer | Shane Lontis <shane.lontis@oracle.com> | 2020-09-26 07:31:59 +1000 |
| commit | 3786d74868fe440250f902ce1a78974136ca9304 (patch) | |
| tree | 14b99e0d58685d1a46482f6f80558113f5b5fa11 /util | |
| parent | fa9e541d49b812549d56c03852290a86aa1645ff (diff) | |
| download | openssl-3786d74868fe440250f902ce1a78974136ca9304.zip openssl-3786d74868fe440250f902ce1a78974136ca9304.tar.gz openssl-3786d74868fe440250f902ce1a78974136ca9304.tar.bz2 | |
en EVP_PKEY_CTX_set_rsa_keygen_pubexp() BIGNUM management
Fixes #12635
As discussed in the issue, supporting the set0-like semantics long-term is not necessarily desirable, although necessary for short-term compatibility concerns. So I've deprecated the original method and added an equivalent that is explicitly labelled as set1.
I tried to audit existing usages of the (now-deprecated) API and update them to use set1 if that appeared to align with their expectations.
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Shane Lontis <shane.lontis@oracle.com>
(Merged from https://github.com/openssl/openssl/pull/12917)
Diffstat (limited to 'util')
| -rw-r--r-- | util/libcrypto.num | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/util/libcrypto.num b/util/libcrypto.num index db4a1aa..7a0965b 100644 --- a/util/libcrypto.num +++ b/util/libcrypto.num @@ -4984,7 +4984,8 @@ OSSL_CMP_MSG_read ? 3_0_0 EXIST::FUNCTION:CMP OSSL_CMP_MSG_write ? 3_0_0 EXIST::FUNCTION:CMP EVP_PKEY_gen ? 3_0_0 EXIST::FUNCTION: EVP_PKEY_CTX_set_rsa_keygen_bits ? 3_0_0 EXIST::FUNCTION:RSA -EVP_PKEY_CTX_set_rsa_keygen_pubexp ? 3_0_0 EXIST::FUNCTION:RSA +EVP_PKEY_CTX_set_rsa_keygen_pubexp ? 3_0_0 EXIST::FUNCTION:DEPRECATEDIN_3_0,RSA +EVP_PKEY_CTX_set1_rsa_keygen_pubexp ? 3_0_0 EXIST::FUNCTION:RSA EVP_PKEY_CTX_set_rsa_keygen_primes ? 3_0_0 EXIST::FUNCTION:RSA NCONF_new_with_libctx ? 3_0_0 EXIST::FUNCTION: CONF_modules_load_file_with_libctx ? 3_0_0 EXIST::FUNCTION: |