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:
The current draft version of FIPS 186-5 says in Appendix E:

"ANSI X9.31 was withdrawn, so X9.31 RSA signatures were removed from this standard"

We should reject them or provide an indicator. It's currently unclear whether we will need this right now, or when FIPS 186-5 moves out of draft status.


Version-Release number of selected component (if applicable):
3.0.1-43.el9_0

How reproducible:
Attempt to create or verify an X9.31 signature.

Steps to Reproduce:
1. openssl genpkey -algorithm RSA -pkeyopt rsa_keygen_bits:2048 -out rsa2048.pem
2. openssl dgst -sha256 -sign rsa2048.pem -sigopt rsa_padding_mode:x931 -out rsa2048.pem.sha256sig rsa2048.pem
3. openssl dgst -sha256 -prverify rsa2048.pem -sigopt rsa_padding_mode:x931 -signature rsa2048.pem.sha256sig rsa2048.pem

Actual results:
Signing succeeds. Verification prints: "Verified OK"

Expected results:
80BB7833A87F0000:error:0200008A:rsa routines:RSA_padding_check_PKCS1_type_1:invalid padding:crypto/rsa/rsa_pk1.c:75:

Additional info:
https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.186-5-draft.pdf.
I'll follow up with the lab on whether this will apply now or later.

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 (Low: openssl security and bug fix update), 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/RHSA-2023:2523