RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1984842 - gnupg2: FTBFS due to test suite failure: <standard>tests/openpgp/ecc.scm
Summary: gnupg2: FTBFS due to test suite failure: <standard>tests/openpgp/ecc.scm
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: gnupg2
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: beta
: 9.0
Assignee: Jakub Jelen
QA Contact: Stanislav Zidek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-22 10:36 UTC by Florian Weimer
Modified: 2022-05-17 15:39 UTC (History)
2 users (show)

Fixed In Version: gnupg2-2.3.3-1.el9
Doc Type: No Doc Update
Doc Text:
Rebase package(s) to version: 2.3.3 Highlights, important fixes, or notable enhancements: * Fix Let's Encrypt certificate chain validation. * remove the gpg-zip tool * disabled internal ccid driver to avoid clashing with system pcscd * many bugfixes https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=blob;f=NEWS;h=d2bb9cbbed9126893b1c019045acf428e752670a;hb=61ac580a2075564bc775b6764a239dad5e336251
Clone Of:
Environment:
Last Closed: 2022-05-17 15:37:05 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
build.log (557.52 KB, text/plain)
2021-07-22 10:36 UTC, Florian Weimer 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CRYPTO-5342 0 None None None 2021-11-19 12:34:57 UTC
Red Hat Product Errata RHBA-2022:3902 0 None None None 2022-05-17 15:37:10 UTC

Description Florian Weimer 2021-07-22 10:36:46 UTC 
Created attachment 1804435 [details]
build.log

Rebuilding gnupg2-2.3.1-1.el9 fails with this error:

Checking ECC encryption and decryption 
    > plain-1 ..gpg: encrypted with nistp384 key, ID AA8B938F9A201946, created 2011-02-09
      "ec_dsa_dh_384 <openpgp>"
gpg: public key decryption failed: Corrupted protection
gpg: decryption failed: Corrupted protection
: (() ((throw (:stderr result)) (call-popen cmd input)))
0: #<CLOSURE>
1: tests.scm:443: (apply throw error)
FAIL: <standard>tests/openpgp/ecc.scm

This may be related to a glibc update. I will try to gather more details.
Comment 1 Florian Weimer 2021-07-22 14:04:41 UTC 
The build failure is sporadic, but can be reproduced with:

cd /builddir/build/BUILD/gnupg-2.3.1/tests/openpgp
while LC_ALL=C EXEEXT= PATH="../gpgscm:/builddir/.local/bin:/builddir/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/sbin" abs_top_srcdir="/builddir/build/BUILD/gnupg-2.3.1" objdir="/builddir/build/BUILD/gnupg-2.3.1" GPGSCM_PATH="/builddir/build/BUILD/gnupg-2.3.1/tests/gpgscm" /builddir/build/BUILD/gnupg-2.3.1/tests/gpgscm/gpgscm   /builddir/build/BUILD/gnupg-2.3.1/tests/openpgp/run-tests.scm ecc.scm ; do : ; done

(In a build chroot.)

I've seen one x86-64 failure. It could be related to bit patterns, similar to the MPI padding problem in OpenPGP and this upstream issue: https://dev.gnupg.org/T5163
Comment 2 Florian Weimer 2021-07-23 15:00:55 UTC 
Since the build failure is so rare, I do not consider this bug a blocker for the mass rebuild anymore.
Comment 6 Jakub Jelen 2021-11-19 11:07:17 UTC 
I got the same failure today when building the update for centos 9 stream:

https://kojihub.stream.rdu2.redhat.com/koji/taskinfo?taskID=784660

```
Checking ECC encryption and decryption 
    > plain-1 ..gpg: encrypted with nistp384 key, ID AA8B938F9A201946, created 2011-02-09
      "ec_dsa_dh_384 <openpgp>"
gpg: public key decryption failed: Corrupted protection
gpg: decryption failed: Corrupted protection
: (() ((throw (:stderr result)) (call-popen cmd input)))
0: #<CLOSURE>
1: tests.scm:443: (apply throw error)
FAIL: <standard>tests/openpgp/ecc.scm 
```

It failed only on i386, while already worked on other arches. Your failure was on s390x so I will try to have a better look into this.
Comment 7 Jakub Jelen 2021-11-19 11:21:36 UTC 
It looks like this is fixed with https://dev.gnupg.org/rG5b1806454c03b3b493222f405ffced80a5d430ad which is for some reason missing from the 2.3.1 release we have in RHEL9. I did not see this failure in Fedora ever.

I tried to run the test for some time locally but did not hit the issue even with the 2.3.1

I think the best course of action right now would be rebase to 2.3.3 right now.
Comment 13 errata-xmlrpc 2022-05-17 15:37:05 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: gnupg2), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:3902
Note You need to log in before you can comment on or make changes to this bug.