If you try and set the sslVersionMax higher than the default range, but within the supported range, you would still get an error and the server would reset the max to "default" max value.
Fix Description:
Keep track of both the supported and default SSL ranges, and correctly use each range for value validation. If the value is outside the supported range, then use default value, etc, but do not check the requested range against the default range. We only use the default range if there is no specified min or max in the config, or if a invalid min or max value is set in the config.
Also, refactored the range variable names to be more accurate:
enabledNSSVersions --> defaultNSSVersions
emin, emax --> dmin, dmax
Also fixed a warning in lib389 about deprecated regex expression.
Bug Description:
If you try and set the sslVersionMax higher than the default range, but within the supported range, you would still get an error and the server would reset the max to "default" max value.
Fix Description:
Keep track of both the supported and default SSL ranges, and correctly use each range for value validation. If the value is outside the supported range, then use default value, etc, but do not check the requested range against the default range. We only use the default range if there is no specified min or max in the config, or if a invalid min or max value is set in the config.
Also, refactored the range variable names to be more accurate:
Also fixed a warning in lib389 about deprecated regex expression.
relates: https://pagure.io/389-ds-base/issue/51129