Add config_diagnostics to our configuration files.
authorPauli <pauli@openssl.org>
Wed, 28 Jul 2021 23:55:09 +0000 (09:55 +1000)
committerPauli <pauli@openssl.org>
Tue, 3 Aug 2021 22:15:14 +0000 (08:15 +1000)
commit92c03668c0cd77434006b613e3429888a0a8ecfe
treeef15d575c88ddc3ec5f88c7696849419012fcfe3
parent6b38d7dc1bccc708279ca5091ebc28cd4bdf225d
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)
20 files changed:
apps/openssl-vms.cnf
apps/openssl.cnf
demos/bio/accept.cnf
demos/bio/cmod.cnf
demos/bio/connect.cnf
demos/certs/apps/apps.cnf
demos/certs/ca.cnf
test/CAtsa.cnf
test/ca-and-certs.cnf
test/ct/log_list.cnf
test/default-and-fips.cnf
test/default-and-legacy.cnf
test/default.cnf
test/fips-and-base.cnf
test/fips.cnf
test/legacy.cnf
test/provider_internal_test.cnf.in
test/proxy.cnf
test/smime-certs/ca.cnf
test/sysdefault.cnf