ssl: Correct SNI handling for TLS-1.3 only server#11198
Open
IngelaAndin wants to merge 1 commit into
Open
Conversation
Contributor
CT Test Results 2 files 66 suites 25m 25s ⏱️ Results for commit 81c5862. ♻️ This comment has been updated with latest results. To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass. See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally. Artifacts
// Erlang/OTP Github Action Bot |
IngelaAndin
force-pushed
the
ingela/ssl/tls-13-sni/OTP-20174
branch
from
ad46a71 to
e876078
Compare
Could cause fault selection of cert and key to be picked when supported signature algorithms are changed by SNI based options update, most probably ending up with a connection error.
IngelaAndin
force-pushed
the
ingela/ssl/tls-13-sni/OTP-20174
branch
from
e876078 to
81c5862
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Could cause fault selection of cert and key to be picked when supported signature algorithms are changed by SNI based options update, most probably ending up with a connection error.