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.
Bug 1654645 - fips-mode-setup --disable is incomplete
Summary: fips-mode-setup --disable is incomplete
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: crypto-policies
Version: 8.0
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: 8.0
Assignee: Tomas Mraz
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-29 10:30 UTC by Ondrej Moriš
Modified: 2018-11-30 10:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 08:35:18 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Ondrej Moriš 2018-11-29 10:30:39 UTC 
Description of problem:

Disabling FIPS mode using fips-mode-setup --disable has the following issues:

a) /etc/system-fips is not deleted
   
b) dracut fips modules is not removed and initramsfs is not 
   re-generated 

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

crypto-policies-20181026-1.gitcc78cb7.el8.noarch

How reproducible:

Always

Steps to Reproduce:

1. Enable fips mode: fips-mode-setup --enable
2. Reboot
3. Disable fips mode: fips-mode-setup --disable
4. Reboot
5. Check dracut configuration, initramfs and /etc/system-fips.

Actual results:

Correct:

* Bootloader configuration is upated correctly
* FIPS mode is turned-off in kernel

Incorrect:

* /etc/system-fips is present
* etc/system-fips is present in initramfs
* dracut contains fips module 
* initramfs created in step (1) is not updated in (3)

Expected results:

* Bootloader configuration is upated correctly
* FIPS mode is turned-off in kernel
* /etc/system-fips is not present
* etc/system-fips is not present in initramfs
* dracut does not contains fips module 
* initramfs is re-generated in (3)

Additional info:

Moreover, fips-mode-setup --check does not detect this inconsistency (reports that FIPS mode is disabled and returns 0).
Comment 1 Tomas Mraz 2018-11-30 08:35:18 UTC 
Yes, this is expected behavior implemented as required by FIPS 140-2 Implementation Guidance. The effect of fips-finish-install is and must be irreversible.
Comment 5 Ondrej Moriš 2018-11-30 10:53:22 UTC 
Thank you both. I also discussed with this with Tomas privately and now it makes sense to me. I did checked documentation and man page FIPS-FINISH-INSTAL(8) is quite clear about this: "[T]he completion of the installation cannot be undone. The system has to be reinstalled if the FIPS modules are not supposed to be installed anymore." Since we cannot really expect anyone to toggle between FIPS mode enabled and disabled I think this explanation is sufficient (in a combination with fips-mode-setup(8) man page). We should only make sure that components related to modules behave the same way as on the system where FIPS mode was never turned on.
Note You need to log in before you can comment on or make changes to this bug.