Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
ACVP testing uses an s-expression of "(genkey(rsa(nbits 4:%u)(test-parms(e %zu:%s)(p %%b)(q %%b))))" with a specified e, p and q and passes this to gcry_pk_genkey(). This triggers a special mode inside the key generation that will eventually return a key with p=q=0.
This causes the pairwise consistency test implemented in test_keys_fips() to fail, because a key with p=q=0 cannot be used to sign data and verify the signature.
The test failure causes libgcrypt to transition into the FIPS fatal error mode, which eventually leads to a call of abort(3) during execution of ACVP tests.
Version-Release number of selected component (if applicable):
libgcrypt-1.10.0-5.el9_0
How reproducible:
Run ACVP tests, or call gcry_pk_genkey() in FIPS mode with the s-expression mentioned above.
Actual results:
"self-test after key generation failed", libgcrypt transitions into fatal error state, subsequent calls trigger abort(3).
Expected results:
No abort, either because
- ACVP tests can be modified to use a different approach, or
- the PCT is not run when test-parms is specified, or
- the failing PCT does not move the library into fatal error mode