Public bug reported: [ Impact ]
gpg in Noble (2.4.4) and Resolute (2.4.8) exits with code 2 when verifying a clearsigned file whose armored signature has no CRC24 checksum line and no base64 "=" padding (i.e. signature length divisible by 3). The signature is reported as "Good signature", but gpg also prints "no valid OpenPGP data found." and exits non-zero. The CRC24 line is optional per RFC 9580, so these files are valid. This breaks tools that rely on gpg's exit status, e.g. reprepro / Landscape 24.04 mirroring https://packages.microsoft.com/ubuntu/26.04/prod/dists/resolute/InRelease. Fixed upstream under https://dev.gnupg.org/T7071. Stonking is not affected. [ Test Plan ] TBD [ Where problems could occur ] TBD [ Other Info ] TBD ** Affects: gnupg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2173093 Title: gpg --verify fails with "no valid OpenPGP data found" on armored signatures without CRC24 checksum or base64 padding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/2173093/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
