Matt Caswell d40b42ab4c Maintain strict type discipline between the core and providers ... A provider could be linked against a different version of libcrypto than the version of libcrypto that loaded the provider. Different versions of libcrypto could define opaque types differently. It must never occur that a type created in one libcrypto is used directly by the other libcrypto. This will cause crashes. We can "cheat" for "built-in" providers that are part of libcrypto itself, because we know that the two libcrypto versions are the same - but not for other providers. To ensure this does not occur we use different types names for the handful of opaque types that are passed between the core and providers. Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/11758)		2020-05-16 17:10:03 +01:00
..
build.info	Add pairwise consistency self tests to asym keygenerators	2020-03-03 14:02:36 +10:00
fipsprov.c	Maintain strict type discipline between the core and providers	2020-05-16 17:10:03 +01:00
self_test_data.inc	Amend references to "OpenSSL license"	2020-04-29 15:27:22 +02:00
self_test_kats.c	Amend references to "OpenSSL license"	2020-04-29 15:27:22 +02:00
self_test.c	Maintain strict type discipline between the core and providers	2020-05-16 17:10:03 +01:00
self_test.h	Amend references to "OpenSSL license"	2020-04-29 15:27:22 +02:00