openssl - Mirror of https://github.com/openssl/openssl

Age	Commit message (Collapse)	Author
2023-09-07	Copyright year updates	Matt Caswell
	Reviewed-by: Richard Levitte <levitte@openssl.org> Release: yes
2023-04-21	Replaced '{ 0, NULL }' with OSSL_DISPATCH_END in OSSL_DISPATCH arrays	Irak Rigia
	Fixes #20710 Reviewed-by: Paul Dale <pauli@openssl.org> Reviewed-by: Richard Levitte <levitte@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/20745)
2020-10-16	null prov: fix gettable param array type.	Pauli
	Reviewed-by: Nicola Tuveri <nic.tuv@gmail.com> (Merged from https://github.com/openssl/openssl/pull/13084)
2020-09-12	provider: add an 'is_running' call to all providers.	Pauli
	It can be accessed (read only) via the status parameter. Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from https://github.com/openssl/openssl/pull/12801)
2020-06-24	Rename <openssl/core_numbers.h> -> <openssl/core_dispatch.h>	Dr. Matthias St. Pierre
	Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/12222)
2020-05-16	Maintain strict type discipline between the core and providers	Matt Caswell
	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-04-09	Add a null provider which implements no algorithms.	Pauli
	By loading the null provider into the default context, it is possible to verify that it is not accidentally being used. Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/11488)