Repository navigation
Conversation
XMLDSig 6.6.4 applies the enveloped signature transform only to a node-set from its parent XML document, and 6.6.3 makes here() an error otherwise. A transform that returns octets has them parsed into a new document for the next transform, so enveloped-signature can't conform when it follows one. xmlsec rejects that order and the JDK's digest doesn't match; only .NET verifies it. Print a DeprecationWarning when enveloped-signature is applied after octets were parsed, when signing and when verifying, so the order can throw in 7.0. The README said the reference processing model requires this order to work; it now says to list enveloped-signature first. https://www.w3.org/TR/xmldsig-core1/#sec-EnvelopedSignature Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 38 minutes. View limit detailsLimit details: You’ve used all 2 included reviews currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #649 +/- ##
==========================================
+ Coverage 86.36% 86.42% +0.06%
==========================================
Files 9 9
Lines 1283 1289 +6
Branches 335 337 +2
==========================================
+ Hits 1108 1114 +6
Misses 100 100
Partials 75 75 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This was referenced Oct 4, 2026
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
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.
Fixes #648. Refs #647.
A
Referencethat listsenveloped-signatureafter a canonicalization, such as[exc-c14n, enveloped-signature], signs and verifies, and the README says the reference processing model requires that. XMLDSig §6.6.4 applies the transform only to "a node-set from its parent XML document". After a canonicalization the library gives it a document parsed from octets, which isn't that.I signed
<root><x>1</x></root>withmasterin both orders:[enveloped-signature, exc-c14n][exc-c14n, enveloped-signature]masterSystem.Security.Cryptography.Xml6.0.1javax.xml.crypto.dsigThis PR deprecates the order so that 7.0 can reject it (#647):
enveloped-signatureafter octets were parsed prints theDeprecationWarningXML_CRYPTO_ENVELOPED_SIGNATURE_AFTER_CANONICALIZATION. It fires incomputeSignature(),checkSignature()andgetCanonXml(), once per process. The order still signs and verifies, with the same output.enveloped-signaturefirst, and that the other order is deprecated and will throw in 7.0.The warning has no test, like the other deprecations. The existing tests of this order stay until 7.0 removes it, and they print the warning once in the test output.
Checks
npm run build && npm test && npm run lintpass (550 tests).[exc-c14n, enveloped-signature]when signing and when verifying, and not for[enveloped-signature, exc-c14n].This is for 6.4, so it should merge after #642.
🤖 Generated with Claude Code