Remove TLSv1 and TLSv1.1 and add TLSv1.3 from HTTPS (SSL) Setup #641
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
In 2022, TLSv1 and TLSv1.1 is insecure.
mktakuya
changed the title
|
The concept of this seems fine, so I'll merge this then follow it up with a subsequent PR to add some further relevant TLS changes. 😄 |
justinclift
approved these changes
Sep 23, 2024
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.
I setup ssl with this document.
HTTPS (SSL) Setup
I found deprecated setting in example of nginx.conf.
In 2022, TLSv1 and TLSv1.1 is insecure.
I’d recommend update this document.