You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
WIP. The idea here is to build a testcase where the chain contains a certificate with an explicit EC point encoding, rather than a namedCurve encoding. This should be rejected by CABF-conforming validators.
Blockers:
Cryptography (rightfully) doesn't support loading these keys
I refuse to write this testcase by hand with openssl req I gave up and did it.
crypto/x509 also reasonably doesn't allow this, which suggests that I'm asking for two incompatible things (an implementation that's good enough for me to build this testcase with, but bad enough that it'll accept an explicit curve encoding). So I'm shelving this for now.
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.
WIP.The idea here is to build a testcase where the chain contains a certificate with an explicit EC point encoding, rather than anamedCurve
encoding. This should be rejected by CABF-conforming validators.Blockers:
Cryptography (rightfully) doesn't support loading these keysI refuse to write this testcase by hand withI gave up and did it.openssl req