Resolve XML-encoded carriage returns during signature validation (2.x) #578
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
mhassan1
changed the title
mhassan1
changed the title
cjbarth
reviewed
Mar 29, 2021
cjbarth
approved these changes
Mar 30, 2021
|
Is there a planned 2.x release that will include this? |
|
Done @mhassan1 |
Merged
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.
Description
This is a 2.x backport of #576.
Resolves #575. See that issue for background.
This adds XML normalization to
validateSignatureForCertbefore sending it toxml-crypto. It usesDOMParserfor normalization tasks such as replacement of XML-encoded entities ( ) with their actual representations (carriage return).Checklist: