diff options
| author | Neil Horman <nhorman@openssl.org> | 2023-12-01 14:02:09 -0500 |
|---|---|---|
| committer | Neil Horman <nhorman@openssl.org> | 2023-12-21 09:22:40 -0500 |
| commit | 506ff20662a228b17840f0b49865a927a45c2908 (patch) | |
| tree | fa99ab163899cb138800889aea431aa364c588ee /test/default-and-fips.cnf | |
| parent | 5528bfbc647c68b6e03262099830ddd1c49dfa23 (diff) | |
Make the activate setting more intuitive
Currently, a provider is activated from our config file using the
activate parameter. However, the presence of the config parameter is
sufficient to trigger activation, leading to a counterintuitive
situation in which setting "activate = 0" still activates the provider
Make activation more intuitive by requiring that activate be set to one
of yes|true|1 to trigger activation. Any other value, as well as
omitting the parameter entirely, prevents activation (and also maintains
backward compatibility.
It seems a bit heavyweight to create a test specifically to validate the
plurality of these settings. Instead, modify the exiting openssl config
files in the test directory to use variants of these settings, and
augment the default.cnf file to include a provider section that is
explicitly disabled
Reviewed-by: Tomas Mraz <tomas@openssl.org>
Reviewed-by: Matthias St. Pierre <Matthias.St.Pierre@ncp-e.com>
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/22906)
Diffstat (limited to 'test/default-and-fips.cnf')
| -rw-r--r-- | test/default-and-fips.cnf | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/default-and-fips.cnf b/test/default-and-fips.cnf index 2ca6487fd2..71af0a385a 100644 --- a/test/default-and-fips.cnf +++ b/test/default-and-fips.cnf @@ -13,4 +13,4 @@ default = default_sect fips = fips_sect [default_sect] -activate = 1 +activate = yes |