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. ** Summary changed: - GnuPG 1.4 requires a patch for GCC 5 + GnuPG 1.4/2.0 requires a patch for GCC 5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501634 Title: GnuPG 1.4/2.0 requires a patch for GCC 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1501634/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
