Add new security policy (20250211) #5111
Merged
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
|
2nd commit adds a new cert with a sha384/p-384 key which is compatible with rfc9151.... I can switch that to using the permutations certificate+key (under tests/pems/permutations/ec_ecdsa_p384_sha384) if that's preferred. |
Mark-Simulacrum
force-pushed
the
add-20250211
branch
from
f43a4ce to
efe3ef2
Compare
goatgoose
reviewed
Feb 17, 2025
lrstewart
reviewed
Feb 17, 2025
lrstewart
reviewed
Feb 17, 2025
goatgoose
approved these changes
Feb 17, 2025
Mark-Simulacrum
force-pushed
the
add-20250211
branch
from
e77df4f to
79f45ab
Compare
lrstewart
approved these changes
Feb 17, 2025
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.
Release Summary:
Adds
20250211, a TLS 1.3-exclusive security policy intended for RFC 9151 migration.Resolved issues:
n/a
Description of changes:
This PR adds a new security policy that is similar/mix of default_tls13 and rfc9115, but with a minimum protocol support of TLS 1.3. As tested, it is compatible with default_tls13 and rfc9115, making it a middle ground for migration towards rfc9115.
Call-outs:
n/a
Testing:
Added a unit test verifying the compatibility -- I'm hoping it runs in CI since locally I think I don't have TLS 1.3 support for it to run successfully.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.