openssl/providers/nullprov.c, branch openssl-3.5.6

3.5-POST-CLANG-FORMAT-WEBKIT

2025-12-09T09:40:50Z

Reviewed-by: Neil Horman Reviewed-by: Saša Nedvědický Reviewed-by: Nikola Pajkovsky (Merged from https://github.com/openssl/openssl/pull/29262)

Copyright year updates

2023-09-07T08:59:15Z

Reviewed-by: Richard Levitte Release: yes

Replaced '{ 0, NULL }' with OSSL_DISPATCH_END in OSSL_DISPATCH arrays

2023-04-21T14:19:11Z

Fixes #20710 Reviewed-by: Paul Dale Reviewed-by: Richard Levitte Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/20745)

null prov: fix gettable param array type.

2020-10-16T00:33:38Z

Reviewed-by: Nicola Tuveri (Merged from https://github.com/openssl/openssl/pull/13084)

provider: add an 'is_running' call to all providers.

2020-09-12T06:46:20Z

It can be accessed (read only) via the status parameter. Reviewed-by: Matt Caswell (Merged from https://github.com/openssl/openssl/pull/12801)

Rename ->

2020-06-24T20:01:22Z

Reviewed-by: Richard Levitte (Merged from https://github.com/openssl/openssl/pull/12222)

Maintain strict type discipline between the core and providers

2020-05-16T16:10:03Z

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 (Merged from https://github.com/openssl/openssl/pull/11758)

Add a null provider which implements no algorithms.

2020-04-09T07:12:35Z

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 Reviewed-by: Richard Levitte (Merged from https://github.com/openssl/openssl/pull/11488)