ismail at namtrac
Apr 27, 2011, 11:31 PM
Post #3 of 4
(243 views)
Permalink
|
|
Re: gpgme 1.30 fails when tested with gnupg 2.0.17
[In reply to]
|
|
Hi;
On Thu, Apr 28, 2011 at 12:26 AM, Marcus Brinkmann <
marcus.brinkmann [at] ruhr-uni-bochum> wrote:
> On 04/27/2011 03:39 PM, İsmail Dönmez wrote:
> > Hi;
> >
> > 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
> > http://bugs.gentoo.org/show_bug.cgi?id=362645 test passes with gnupg
> 2.0.16
> > which I didn't verify myself personally.
> >
> > Only suspicious commit is
> >
> http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commitdiff;h=398e686085fd40ea3d20e99ff5c83ef27626f1abbut
> > I am not sure if its the culprit.
>
> Yeah I know, I checked in an update to the test suite yesterday, which is
> targeted towards GnuPG 2.1, and that should fix this one (but as I didn't
> test
> GnuPG 2.0 yet, there may be other problems remaining).
>
I cherry picked the t-encrypt-sign part, thanks!
Regards,
ismail
|
signature.asc
