gpgme 1.30 fails when tested with gnupg 2.0.17

İsmail Dönmez ismail at
Wed Apr 27 15:39:00 CEST 2011


Testing gpgme 1.30 with gnupg 2.0.17 fails in t-encrypt-sign test:

Wrong hash algorithm reported: 3
FAIL: t-encrypt-sign

The test expects SHA1 but the message is signed with RMD160. According to test passes with gnupg 2.0.16
which I didn't verify myself personally.

Only suspicious commit is;a=commitdiff;h=398e686085fd40ea3d20e99ff5c83ef27626f1abbut
I am not sure if its the culprit.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20110427/e378f319/attachment.htm>

More information about the Gnupg-devel mailing list