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 code that is python-cryptography in version 3.4.7-6 does not detect fips mode on rhel 9 because it has not been updated for OpenSSL 3.0.

https://github.com/pyca/cryptography/blob/3.4.x/src/cryptography/hazmat/backends/openssl/backend.py#L243-L249 

It needs to be updated to something that looks like :

https://github.com/pyca/cryptography/blob/main/src/cryptography/hazmat/backends/openssl/backend.py#L211-L222

Note: this is blocking OpenStack testing of FIPS mode in centos/rhel9.

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


How reproducible:

Always

Steps to Reproduce:
1. On a FIPS mode Centos-9 machine

cheimes> >>> from cryptography.hazmat.backends.openssl import backend
<cheimes> >>> backend._is_fips_enabled()
<cheimes> False
<cheimes> $ cat /proc/sys/crypto/fips_enabled 
<cheimes> 1

Actual results:


Expected results:


Additional info:

OpenSSL 3.0.0 FIPS fixes were added in upstream PR https://github.com/pyca/cryptography/pull/6012.

Verifying using the latest RHEL 9.0 nightly repos

[root@ci-vm-10-0-137-195 ~]# rpm -qa python3-cryptography
python3-cryptography-36.0.1-1.el9_0.x86_64
[root@ci-vm-10-0-137-195 ~]# python3
Python 3.9.10 (main, Feb  9 2022, 00:00:00) 
[GCC 11.2.1 20220127 (Red Hat 11.2.1-9)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from cryptography.hazmat.backends.openssl import backend
>>> backend._is_fips_enabled()
True
>>> from cryptography.hazmat.primitives.ciphers import algorithms, modes
>>> backend.cipher_supported(algorithms.TripleDES(b"\x00" * 8), modes.CBC(b"\x00" * 8))
False
>>> 
[root@ci-vm-10-0-137-195 ~]# sysctl crypto.fips_enabled
crypto.fips_enabled = 1
[root@ci-vm-10-0-137-195 ~]# 

Based on above results marking bugzilla verified.

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: python-cryptography), 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:2580