Websocket to support TLSv1.2 #207
Merged
Conversation
This file contains 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
It was noticed that websocket clients including Chrome and Firefox had stopped supporting or rejecting TLSv1 since it's an OBSOLETE PROTOCOL.
|
Thanks. I think we should stop supporting TLSv1.0 and TLSv1.1 too, both for server and for client. |
|
By the way, perhaps we should initiate the contexts with |
abitmore
approved these changes
Sep 13, 2020
This was referenced Sep 20, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It was noticed that websocket clients including Chrome and Firefox had stopped supporting or rejecting TLSv1 since it's an OBSOLETE PROTOCOL.