GnuPG 1.4/2.0 requires a patch for GCC 5

[NIIBE Yutaka]

Hello,

I am a upstream developer of GnuPG, and we got a bug report.

https://lists.gnupg.org/pipermail/gnupg-devel/2015-September/030334.html
https://lists.gnupg.org/pipermail/gnupg-devel/2015-October/030336.html

I committed a fix to upstream repository for 1.4 and 2.0.

Then, I realized that Ubuntu uses GCC 5 for building gnupg. Thus, reporting.

I'm not sure if this bug is reproducible on Ubuntu. It is reproducible on my Debian machine.
Please check.

[NIIBE Yutaka (gniibe)]

This bug is fixed in upstream.

GnuPG 1.4:
http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=6db18e29eb81b37ed6feb592add77d492c60fc35

GnuPG 2.0:
http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=b1653a4083b91cfa85d90f59612fa1c3f4d51778

It had been fixed in development branch before, and the fix was intended to silence a warning at that time. Because of that, the commit log doesn't directly address it's a bug.

Now with GCC 5, we have a concrete example which hits the bug. Namely, OpenPGP-compliant valid signature might be
regected.

[Marc Deslauriers (mdeslaur)]

Thanks for reporting this. Looks like xenial already contains 1.4.20, which includes the fix.

I'll take care of fixing gnupg2.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnupg2 - 2.0.28-3ubuntu2

---------------
gnupg2 (2.0.28-3ubuntu2) xenial; urgency=medium

  * debian/gcc5-fix.patch: add upstream fix for an optimization issue when
    compiling with gcc 5. (LP: #1501634)

 -- Marc Deslauriers <email address hidden> Tue, 09 Feb 2016 16:11:42 -0500