docs: add comments about sslv3 weaknesses#5777
Merged
WesleyRosenblum merged 2 commits intomainfrom Mar 10, 2026
Merged
Conversation
alexw91
approved these changes
Mar 9, 2026
kaukabrizvi
approved these changes
Mar 10, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Goal
Reduce misconceptions about the security implications of code related to SSLv3
Why
SSLv3 contains several weaknesses that make it not recommended for use. These weaknesses should not be interpreted as flaws in s2n-tls's implementation of SSLv3, as they are inherent to the protocol itself.
How
Adds comments regarding SSLv3's lack of validation of padding and use of weak hash algorithms
Testing
Doc only change
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.