srd90

I suggested https://github.com/node-saml/xml-crypto/issues/486#issuecomment-2637904015 as answer to your question's `#xD;` part. About splitting every 76th character (the `\n` part of your question)...dunno if I read spec correctly but I get a...

1. Give example of signed xml document (along with certificate of key that was used to sign) that passes shell script which uses `xmlsec1 --verify ...` (construct shell script so...

Here is example how xmlsec1 was used at one case as a reference implementation: https://github.com/node-saml/xml-crypto/issues/212#issuecomment-1949310736 Note: that case was related to signing (and more specifically to find out lack of...

Now....how is that related to xml-crypto? Are you saying that xml-crypto fails to verify signature? Does xmlsec1 verify that signature? Or Are you saying that if xml-crypto would be used...

>It is all in the aws repo Good. Then there chance that you hand out direct link. No-one else except youself is getting any money to run around to gather...

1. Show full output (signed xml document) of your xml-crypto fork and your java sw. Use same input (private key and input xml) for both cases. 2. I am especially...

4. tell us what xmlsec1 says about your java and xml-crypto versions of signed xml even if they have different signature (from actual value point of view or from "layout"...

Adding more context to this issue for future generations who might land here via some search engine. Based on content of this comment: https://github.com/node-saml/xml-crypto/issues/486#issuecomment-2638329029 This issue seems to be at...

I did not test (run) your code but one thing caught my I immediately. Quote from your issue report >```javascript > sig.addReference({ > xpath: "/*", > digestAlgorithm: 'http://www.w3.org/2000/09/xmldsig#sha1', > transforms:...

Did you add that transformation and test your stuff? FWIW, if you are conserned about having that extra transformation explicitly listed at resulting xml (which means that your signature block...