Added a warning when the server accepts TLSv1.0 #8
Conversation
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
Author
|
I used "PV006" as the warning ID as it was not being used. My decision was completely arbitrary, feel free to change it. |
I stepped it up even further in #12. Now there is a warning for TLS 1.0 and 1.1 since both are now deprecated. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
There are several issues with TLSv1.0 and it's being deprecated everywhere. The general consensus is that it should not be used anymore and similar tools issue warnings for this.
Reference: https://www.comodo.com/e-commerce/ssl-certificates/tls-1-deprecation.php
Best,
Leandro