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 2026657 - Running fips-mode-setup --enable forces "base" FIPS crypto policy, when module is enabled
Summary: Running fips-mode-setup --enable forces "base" FIPS crypto policy, when modul...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: crypto-policies
Version: 9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Alexander Sosedkin
QA Contact: Ondrej Moriš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-25 12:36 UTC by Jan Pazdziora
Modified: 2022-05-17 16:21 UTC (History)
4 users (show)

Fixed In Version: crypto-policies-20220203-1.gitf03e75e.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 15:54:53 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CRYPTO-6129 0 None None None 2022-02-03 13:52:32 UTC
Red Hat Issue Tracker RHELPLAN-103946 0 None None None 2021-11-25 12:37:59 UTC
Red Hat Product Errata RHBA-2022:3953 0 None None None 2022-05-17 15:55:00 UTC

Description Jan Pazdziora 2021-11-25 12:36:56 UTC 
Description of problem:

When fips-mode-setup --enable is run without first checking fips-mode-setup --is-enabled or --check, the crypto policy is set to FIPS, even if a FIPS policy with module (like FIPS:OSPP) is already set.

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

crypto-policies-scripts-20210922-1.git6fb269b.el9.noarch

How reproducible:

Deterministic.

Steps to Reproduce:
1. Install system with fips=1 kernel command-line parameter.
2. Check that FIPS mode is enabled:
   # fips-mode-setup --check
   FIPS mode is enabled.
3. Set crypto policy to FIPS with module:
   # update-crypto-policies --no-reload --set FIPS:OSPP
   Setting system policy to FIPS:OSPP
   Note: System-wide crypto policies are applied on application start-up.
   It is recommended to restart the system for the change of policies
   to fully take place.
4. Check the configured crypto policy:
   # update-crypto-policies --show && update-crypto-policies --check
   FIPS:OSPP
   The configured policy matches the generated policy
5. Check that FIPS mode is enabled:
   # fips-mode-setup --check
   FIPS mode is enabled.
6. Run fips-mode-setup --enable again, maybe to be extra sure, or by mistake:
   # fips-mode-setup --enable
   Setting system policy to FIPS
   Note: System-wide crypto policies are applied on application start-up.
   It is recommended to restart the system for the change of policies
   to fully take place.
   FIPS mode will be enabled.
   Please reboot the system for the setting to take effect.
7. Check the crypto policy now:
   # update-crypto-policies --show

Actual results:

FIPS

Expected results:

FIPS:OSPP

Additional info:

In the same way fips-mode-setup --check reports success when it finds FIPS:OSPP crypto policy configured, --enable should preserve the policy module if the base policy is FIPS.
Comment 10 errata-xmlrpc 2022-05-17 15:54:53 UTC 
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: crypto-policies), 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:3953
Note You need to log in before you can comment on or make changes to this bug.