GnuPG 1.4/2.0 requires a patch for GCC 5
Bug #1501634 reported by
NIIBE Yutaka
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnupg (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| gnupg2 (Ubuntu) |
Fix Released
|
Undecided
|
Marc Deslauriers | ||
Bug Description
Hello,
I am a upstream developer of GnuPG, and we got a bug report.
https:/
https:/
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.
Revision history for this message
| NIIBE Yutaka (gniibe) wrote | #1 |
| summary: |
- GnuPG 1.4 requires a patch for GCC 5 + GnuPG 1.4/2.0 requires a patch for GCC 5 |
Revision history for this message
| Marc Deslauriers (mdeslaur) wrote | #2 |
| Changed in gnupg (Ubuntu): | |
| status: | New → Fix Released |
| Changed in gnupg2 (Ubuntu): | |
| status: | New → Confirmed |
| assignee: | nobody → Marc Deslauriers (mdeslaur) |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in gnupg2 (Ubuntu): | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
This bug is fixed in upstream.
GnuPG 1.4:
http://
GnuPG 2.0:
http://
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.