fix #5125 allowing for TLS 1.3 only support #5128
Merged
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.
Description
Fixes #5125 by enabling support for TLS 1.3 as well as 1.2 and creating the context off of the latest known version. The other option is to use getInstance("TLS") - but I couldn't determine if that would guarantee the latest support as for older vm, which had 1.3 support added later still appear to default to 1.2.
@vietj can you check how this should be supported with vertx? The are some refinements here related to this, but as far as I can tell TLS 1.2 is still supported even if we specify only TLS 1.3 client support. Should we still be using JdkSSLEngineOptions even if we are also providing the KeyManagers and TrustManagers?
Type of change
test, version modification, documentation, etc.)
Checklist