Set secure wss cipher list #3885
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
jacobkeeler
requested changes
Mar 22, 2022
src/components/transport_manager/src/cloud/websocket_client_connection.cc
Outdated
Show resolved
Hide resolved
…nnection.cc Co-authored-by: Jacob Keeler <jacob.keeler@livioradio.com>
jacobkeeler
approved these changes
Mar 23, 2022
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.
Fixes #3884
This PR is ready for review.
Risk
This PR makes no API changes.
Testing Plan
Connect cloud application using wss with a signed CA.cert
Summary
Sets the ssl context for wss connections to only use "hardened" cipher suites. This prevents the java server from using an insecure key exchange mechanism. Resolves the dh key length issue without reducing the operating systems security level.
CLA