Use secure ciphers and TLS protocols where supported #80
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
JoeChapman
force-pushed
the
remove_insecure_ciphers
branch
from
1d7a326
to
b68b0c4
Compare
…browsers we support
JoeChapman
force-pushed
the
remove_insecure_ciphers
branch
from
b68b0c4
to
2ab740e
Compare
|
@daniel-ac-martin @allandegnan help me debug this? |
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.
Linked to #78 explaining background behind PR.
Aim is to secure sever against attacks that target insecure TLS ciphers.