Add EVP_PKEY_CTX_new_provided()
This works as much as possible EVP_PKEY_CTX_new_id(), except it takes data that's relevant for providers, algorithm name and property query string instead of NID and engine. Additionally, if EVP_PKEY_CTX_new() or EVP_PKEY_CTX_new_id() was called, the algorithm name in the EVP_PKEY context will be set to the short name of the given NID (explicit or the one of the given EVP_PKEY), thereby giving an easier transition from legacy methods to provided methods. The intent is that operations will use this information to fetch provider methods implicitly as needed. Reviewed-by: Tomas Mraz <tmraz@fedoraproject.org> (Merged from https://github.com/openssl/openssl/pull/10184)
This commit is contained in:
parent
1af26e53bc
commit
a07c17ef57
6 changed files with 49 additions and 7 deletions
8
CHANGES
8
CHANGES
|
@ -9,6 +9,14 @@
|
|||
|
||||
Changes between 1.1.1 and 3.0.0 [xx XXX xxxx]
|
||||
|
||||
*) Added functionality to create an EVP_PKEY context based on data
|
||||
for methods from providers. This takes an algorithm name and a
|
||||
property query string and simply stores them, with the intent
|
||||
that any operation that uses this context will use those strings
|
||||
to fetch the needed methods implicitly, thereby making the port
|
||||
of application written for pre-3.0 OpenSSL easier.
|
||||
[Richard Levitte]
|
||||
|
||||
*) The undocumented function NCONF_WIN32() has been deprecated; for
|
||||
conversion details see the HISTORY section of doc/man5/config.pod
|
||||
[Rich Salz]
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue