Bug 1804281

Summary: Enable FIPS mode during crypto-policies installation when kernel is in FIPS mode
Product: Red Hat Enterprise Linux 8 Reporter: Ondrej Moriš <omoris>
Component: crypto-policiesAssignee: Tomas Mraz <tmraz>
Status: CLOSED ERRATA QA Contact: Alexander Sosedkin <asosedki>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.2CC: asosedki, nmavrogi
Target Milestone: rcKeywords: Triaged
Target Release: 8.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: crypto-policies-20200527-4.git63fc906.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-04 01:58:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ondrej Moriš 2020-02-18 15:38:39 UTC 
Description of problem:

When crypto-policy package is installed and kernel is in FIPS mode then crypto-policies should enable FIPS mode as a part of its post-installation scripts.

This is needed especially for RHEL installation in FIPS by anaconda.

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

crypto-policies-20191128-2.git23e1bf1.el8.noarch
Comment 1 Tomas Mraz 2020-05-29 10:01:11 UTC 
So this is what I am going to do to hopefully solve this:

1. in filelist mark /etc/crypto-policies/config as %ghost %config(missingok,noreplace)

2. in %pre of the base package do:

If no /etc/crypto-policies/config is present and /proc/sys/crypto/fips-enabled contains 1
   Put FIPS into /etc/crypto-policies/config
   Symlink all files from /usr/share/crypto-policies/FIPS into /etc/crypto-policies/back-ends

Ondrej or Alex, can you please do QE scoping and add ack?
Comment 10 errata-xmlrpc 2020-11-04 01:58:27 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 (crypto-policies bug fix and enhancement update), 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-2020:4536