Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

xmlsec message imprint error version 1.3.6 vs 1.3.3 #42901

Open
hafedh-trimeche opened this issue Dec 23, 2024 · 1 comment
Open

xmlsec message imprint error version 1.3.6 vs 1.3.3 #42901

hafedh-trimeche opened this issue Dec 23, 2024 · 1 comment
Assignees
@jimwang118
Labels
category:port-bug The issue is with a library, which is something the port should already support depends:upstream-changes Waiting on a change to the upstream project

Comments

@hafedh-trimeche
Copy link

hafedh-trimeche commented Dec 23, 2024 •
edited
Loading

Hello,
Please note that xmlsec version 1.3.3 worked fine for signature.
The verification of a document generated by the version 1.3.6 on
https://signatures-conformance-checker.etsi.org/protected/upload.php?sigtype=xadesconf
generated an error
Image

Error. The message imprint found in the time-stamp token is: de47c9b27eb8d300dbb5f2c353e632c393262cf06340c4fa7f1b40c4cbd36f90. The message imprint computed is: 5cf9641995c3e4a810df29b33c18e3deb8fd9cd3a28d26dcb9f7ecb40f83deef

Please also note that the extension of the uploaded files should be changed to xml

Best regards.
xmlsec-signed-1.3.3.txt
xmlsec-signed-1.3.6.txt
@jimwang118 jimwang118 added the category:port-bug The issue is with a library, which is something the port should already support label Dec 24, 2024
@jimwang118
Copy link
Contributor

This should be an upstream issue, please file an issue upstream.

@jimwang118 jimwang118 added the depends:upstream-changes Waiting on a change to the upstream project label Dec 25, 2024
@hafedh-trimeche hafedh-trimeche mentioned this issue Dec 25, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jimwang118 jimwang118

Labels
category:port-bug The issue is with a library, which is something the port should already support depends:upstream-changes Waiting on a change to the upstream project
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hafedh-trimeche @jimwang118