Enable OpenSSL 3.x as the default in UI #263
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #256 the support for v3 changes is being added. It can be released without making the 3.x branch the default for everyone, allowing some time to offer it as a preview feature, as "opt-in", before settling on that as the new default for anyone and everyone.
This is a followup, to enable the v3.x as our new default, to stage the rollout in two phases — once we're happy with the #256 changes for the current 1.1.1 configs (e.g. where changing dhparams for the current defaults), as well as any feedback on the new changes (leaving out dhparams in favour of handshake automagic selection, and lowering seclevel for
old
via patching the cipherstring) it brings once switched as the new default.