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.
Created attachment 1698632[details]
Screenshot of console during shutdown
Description of problem:
Suppose I have a system in FIPS mode. I want to disable FIPS mode - even though we do not officially support this use case. It always worked and our tools were able to do that since RHEL-8.0. The process is as follows:
0. prerequisite: fips mode is enabled
1. fips-mode-setup --disable
2. rm /etc/system-fips
3. rm /etc/dracut.conf.d/40-fips.conf
4. dracut -vf
5. reboot
This is the procedure that was working fine on RHEL-8.2. But on RHEL-8.3 (Alpha-1.1) reboot will end up in dracut emergency shell after shutdown abort (FATAL FIPS SELFTEST FAILURE), screenshot is attached. Event though abort comes from openssl it is most likely caused by missing hmacs in regenerated initramfs:
Before step 1:
# lsinitrd | grep '\(libcrypto.*hmac\|libssl.*hmac\)'
usr/lib64/.libcrypto.so.1.1.1g.hmac
usr/lib64/.libcrypto.so.1.1.hmac -> .libcrypto.so.1.1.1g.hmac
usr/lib64/.libssl.so.1.1.1g.hmac
usr/lib64/.libssl.so.1.1.hmac -> .libssl.so.1.1.1g.hmac
#
After step 4:
# lsinitrd | grep '\(libcrypto.*hmac\|libssl.*hmac\)'
#
Is there any valid reason to remove hmac files?
Version-Release number of selected component (if applicable):
dracut-049-83.git20200525.el8
How reproducible:
100%
Steps to Reproduce:
See above.
Actual results:
Shutdown failure, dracut emergency shell.
Expected results:
Reboot works and system boot into disable FIPS mode.
*** Bug 1868661 has been marked as a duplicate of this bug. ***
Comment 7RHEL Program Management
2021-12-24 07:27:00 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Created attachment 1698632 [details] Screenshot of console during shutdown Description of problem: Suppose I have a system in FIPS mode. I want to disable FIPS mode - even though we do not officially support this use case. It always worked and our tools were able to do that since RHEL-8.0. The process is as follows: 0. prerequisite: fips mode is enabled 1. fips-mode-setup --disable 2. rm /etc/system-fips 3. rm /etc/dracut.conf.d/40-fips.conf 4. dracut -vf 5. reboot This is the procedure that was working fine on RHEL-8.2. But on RHEL-8.3 (Alpha-1.1) reboot will end up in dracut emergency shell after shutdown abort (FATAL FIPS SELFTEST FAILURE), screenshot is attached. Event though abort comes from openssl it is most likely caused by missing hmacs in regenerated initramfs: Before step 1: # lsinitrd | grep '\(libcrypto.*hmac\|libssl.*hmac\)' usr/lib64/.libcrypto.so.1.1.1g.hmac usr/lib64/.libcrypto.so.1.1.hmac -> .libcrypto.so.1.1.1g.hmac usr/lib64/.libssl.so.1.1.1g.hmac usr/lib64/.libssl.so.1.1.hmac -> .libssl.so.1.1.1g.hmac # After step 4: # lsinitrd | grep '\(libcrypto.*hmac\|libssl.*hmac\)' # Is there any valid reason to remove hmac files? Version-Release number of selected component (if applicable): dracut-049-83.git20200525.el8 How reproducible: 100% Steps to Reproduce: See above. Actual results: Shutdown failure, dracut emergency shell. Expected results: Reboot works and system boot into disable FIPS mode.