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:

This should raise a ValueError in FIPS mode but it doesn't:

    python -c "import hashlib; print(hashlib.md5())"

Looks like python36 hasn't been patched with FIPS support.


Version-Release number of selected component (if applicable):

python36-3.6.8-1.el7.x86_64


How reproducible:

Always


Steps to Reproduce:
1. Enable fips mode in Centos 7
2. Check that fips is enabled (eg sysctl crypto.fips_enabled)
3. Run the command above


Actual results:

No exception.


Expected results:

ValueError


Additional info:

Given the soon to be added python3 package in RHEL, this EPEL package will be retired soon. Hence reassigning.

In RHEL-7 we only cared for the crypto libraries' FIPS validation.
In RHEL-8 we stepped up the game to make the whole distribution FIPS compliant, with as few exceptions as possible.

So the current status is fine by us, no sync is needed, and it is actually unwanted as it may break working customer installations.

Filed a new bug for comment#15:

https://bugzilla.redhat.com/show_bug.cgi?id=1811170

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, 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-2020:1132