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.

python-wheel has a built-in implementation for signing and verifying data using the EdDSA 25519 curve. This curve is currently not a FIPS algorithm, but there are plans to make it FIPS. In either case we can't include python-wheel in any FIPS validated releases.

See:
https://pelc.engineering.redhat.com/reviews/9873/
https://docs.google.com/document/d/1rmQqP4Dhgmaae_29gVoKmczOoobuZP4P4y7ViOBzbG0/edit

This problem can be remedied in the following ways:
1) remove the signing/verification code.
2) switch to using python's crypto module, which uses FIPS validated openssl.
3) disabling the use of signing/verification.

In reviewing the code, the current builds already issue a warning that the functionality is deprecated. The easiest way to compliance is to make the warning a failure to prevent the use of the crypto algorithm.

The maintainer is free to implement any of the three options above based on their customer base and the current upstream direction.

bob

Are we talking about that change? https://github.com/pypa/wheel/commit/d3f5918ccbb1c79e2fc42b7766626a0aa20dc438

If so that was part of wheel 0.32.0 release (we ship 0.31.1 with RHEL7 and RHEL8).

Bob could you verify if that commit addresses the issue?

The bug is fixed. Can we close it?

python3-wheel-0.31.1-5.el7_7 is part of the 7.9 compose, so everything is ok to close this tracker.