feat: additional rfc9151 compat policy without sha1 hmac#5645
Merged
feat: additional rfc9151 compat policy without sha1 hmac#5645
Conversation
CarolYeh910
approved these changes
Dec 2, 2025
raycoll
approved these changes
Dec 2, 2025
jmayclin
reviewed
Dec 2, 2025
jmayclin
approved these changes
Dec 2, 2025
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
4 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
Same as #5615
Why
This adds a transition policy for servers that supports ciphers in 20251114, without SHA1 HMAC ciphers.
How
security_policy_20251117is added. This is identical to 20251114, but with SHA1 HMAC ciphers removed.This PR also expose new policies in s2n_security_policies.h since the previous PR forgot to do so.
Callouts
Testing
Regenerated policy snapshot. Other existing tests continue to pass.
Related
related: #5615
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.