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.
+++ This bug was initially created as a clone of Bug #1950132 +++
Description of problem:
Certmonger uses default OpenSSL encryption algorithms to generate the PKCS12 object used for the local CA. This uses operations that are disallowed under fips, and so the local ca pkcs12 creds file is not generated.
We can fix this by using approved algorithms as in :
https://pagure.io/certmonger/pull-request/198
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--- Additional comment from Ade Lee on 2021-04-15 20:09:36 UTC ---
For additional context, this is used in Openstack to provide the local CA on the undercloud.
--- Additional comment from Rob Crittenden on 2021-04-16 00:03:47 UTC ---
This is fixed upstream in 62a6634867db5d9f79b613055b8788136d4cb41d
certmonger allowed openssl to pick the default key and cert algorithms when calling PKCS12_create. openssl uses PBE-SHA1-RC2-40 by default to encrypt the key which is not FIPS compliant. The upstream change switches to AES-128-CBC for both the cert and key.
This will not replace existing credential files on upgrade. In order to have certmonger generate a new PKCS#12 to store the local CA credentials remove /var/lib/certmonger/local/creds and restart.
To verify that the credentials are compliant run:
# openssl pkcs12 -info -in /var/lib/certmonger/local/creds -noout
Enter Import Password: < enter, there is no password >
MAC: sha1, Iteration 1
MAC length: 20, salt length: 8
PKCS7 Encrypted data: PBES2, PBKDF2, AES-128-CBC, Iteration 2048, PRF hmacWithSHA256
Certificate bag
PKCS7 Data
Shrouded Keybag: PBES2, PBKDF2, AES-128-CBC, Iteration 2048, PRF hmacWithSHA256