crypto/x509: validate certificates with unsorted SET values in RDNs #17
Conversation
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
austinderek
force-pushed
the
master
branch
27 times, most recently
from
121e5bb to
7a1679d
Compare
austinderek
force-pushed
the
master
branch
30 times, most recently
from
7bba745 to
37c78b5
Compare
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.
Added check to ensure SET values in RDNs are sorted in ascending order
as required by ASN.1 DER encoding rules (X.690 section 11.6).
When unsorted SET values are detected, reject the certificate with a
"invalid RDNSequence: SET values not in ascending order" error.
Fixes golang#73743
🔄 This is a mirror of upstream PR #73936