Remove P-521 curve from agent certificate requirements #295
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
chrisn
approved these changes
Sep 8, 2022
|
This was discussed at TPAC 2022 and there were no objections to removing P-521 from the spec given the justifications posted in the associated issue. |
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.
Addresses Issue #277: Consider removing support for P-521
P-521 is a 521-bit elliptic curve that can be used to generate ECDSA certificates. Although it's supported in TLS 1.3, it is not widely used in practice.
See this thread on mozilla.dev.security.policy for some discussion of the issues with P-521. In short it offers little incremental security benefits over P-384, and ECC implementations are likely not very optimized.
So we're not going to make it an option for OSP agent certificates, so implementations don't need to support it.
Preview | Diff