diff options
| author | Richard Levitte <levitte@openssl.org> | 2020-08-18 20:39:45 +0200 |
|---|---|---|
| committer | Richard Levitte <levitte@openssl.org> | 2020-08-20 12:32:00 +0200 |
| commit | 22b814443eea4ef4ea86d5d5677601d6645606d9 (patch) | |
| tree | 8c29025ed8bc952d64f10b5822b78d84574ccc02 /util | |
| parent | 3b1fd0b003572554ad9bb3914527c160bc6a7727 (diff) | |
X509: Add d2i_PUBKEY_ex(), which take a libctx and propq
Just like d2i_PrivateKey() / d2i_PrivateKey_ex(), there's a need to
associate an EVP_PKEY extracted from a PUBKEY to a library context and
a property query string. Without it, a provider-native EVP_PKEY can
only fetch necessary internal algorithms from the default library
context, even though an application specific context should be used.
Reviewed-by: Paul Dale <paul.dale@oracle.com>
(Merged from https://github.com/openssl/openssl/pull/12671)
Diffstat (limited to 'util')
| -rw-r--r-- | util/libcrypto.num | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/util/libcrypto.num b/util/libcrypto.num index b38670b1ab..6aa0109de3 100644 --- a/util/libcrypto.num +++ b/util/libcrypto.num @@ -5262,3 +5262,4 @@ EVP_SIGNATURE_gettable_ctx_params ? 3_0_0 EXIST::FUNCTION: EVP_SIGNATURE_settable_ctx_params ? 3_0_0 EXIST::FUNCTION: EVP_KEYEXCH_gettable_ctx_params ? 3_0_0 EXIST::FUNCTION: EVP_KEYEXCH_settable_ctx_params ? 3_0_0 EXIST::FUNCTION: +d2i_PUBKEY_ex ? 3_0_0 EXIST::FUNCTION: |