openssl/test/provider_internal_test.cnf.in

# Comment out the next line to ignore configuration errors
config_diagnostics = 1

{- use platform -}
openssl_conf = openssl_init

[openssl_init]
providers = providers

[providers]
p_test_configured = p_test_configured

[p_test_configured]
module = {- platform->dso('p_test') -}
activate = 1
greeting = Hello OpenSSL, greetings from Test Provider
Add config_diagnostics to our configuration files. The change to a more configuration based approach to enable FIPS mode operation highlights a shortcoming in the default should do something approach we've taken for bad configuration files. Currently, a bad configuration file will be automatically loaded and once the badness is detected, it will silently stop processing the configuration and continue normal operations. This is good for remote servers, allowing changes to be made without bricking things. It's bad when a user thinks they've configured what they want but got something wrong and it still appears to work. Reviewed-by: Dmitry Belyavskiy <beldmit@gmail.com> (Merged from https://github.com/openssl/openssl/pull/16171) 2021-07-29 07:55:09 +08:00			`# Comment out the next line to ignore configuration errors`
			`config_diagnostics = 1`

Add test for the provider configuration module We reuse test/provider_internal_test.c and test/p_test.c, and get it loaded one more time via the configuration file test/provider_internal_test.conf To support different platform standards regarding module extensions, we generate test/provider_internal_test.conf Reviewed-by: Paul Dale <paul.dale@oracle.com> (Merged from https://github.com/openssl/openssl/pull/8549) 2019-03-31 05:10:39 +08:00			`{- use platform -}`
			`openssl_conf = openssl_init`

			`[openssl_init]`
			`providers = providers`

			`[providers]`
			`p_test_configured = p_test_configured`

			`[p_test_configured]`
			`module = {- platform->dso('p_test') -}`
			`activate = 1`
			`greeting = Hello OpenSSL, greetings from Test Provider`