Richard Levitte 10315851d0 X509: Refactor X509_PUBKEY processing to include provider side keys ... When a SubjectPublicKeyInfo (SPKI) is decoded into an X509_PUBKEY structure, the corresponding EVP_PKEY is automatically added as well. This used to only support our built-in keytypes, and only in legacy form. This is now refactored by making The ASN1 implementation of the X509_PUBKEY an EXTERN_ASN1, resulting in a more manual implementation of the basic support routines. Specifically, the d2i routine will do what was done in the callback before, and try to interpret the input as an EVP_PKEY, first in legacy form, and then using OSSL_DECODER. Fixes #13893 Reviewed-by: Paul Dale <pauli@openssl.org> (Merged from https://github.com/openssl/openssl/pull/14281)		2021-02-24 10:17:14 +01:00
..
crypto	X509: Refactor X509_PUBKEY processing to include provider side keys	2021-02-24 10:17:14 +01:00
internal	provider: add option to load a provider without disabling the fallbacks.	2021-02-23 23:24:41 +10:00
openssl	provider: add option to load a provider without disabling the fallbacks.	2021-02-23 23:24:41 +10:00