signxml: Incorrect signature in 2.10.0
A test in my project revealed that signxml 2.10.0 generates invalid signatures, while 2.9.0 generates correct signatures. The cause is the new excise_empty_xmlns_declarations parameter, which is appropriately set when validating a signature, but it also needs to be set when generating a signature.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 16 (9 by maintainers)
@kislyuk , thanks for looking into this. It takes some time for me to isolate and sanitize a test case.
This test only works with the branch of signxml I created at https://github.com/OpenPaymentNetwork/signxml . The company I’m working with accepts the signatures generated by our branch; it does not accept the signatures generated by signxml 2.10. That’s why I believe our branch is correct and signxml 2.10 is not. I am certainly open to the possibility that we’re calling signxml in some incorrect way.
The private key I included is used only for this test case and nothing else, so there’s no risk in sharing it.