Bug 2130181 - FIPS enabled profiles built in offline mode with image-builder won't boot
Summary: FIPS enabled profiles built in offline mode with image-builder won't boot
Keywords:
Status: MODIFIED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: scap-security-guide
Version: 8.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Vojtech Polasek
QA Contact: BaseOS QE Security Team
URL: https://github.com/ComplianceAsCode/c...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-27 12:30 UTC by Evgeny Kolesnikov
Modified: 2023-08-17 16:14 UTC (History)
7 users (show)

Fixed In Version: scap-security-guide-0.1.69-1.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-135015 0 None None None 2022-09-27 12:49:37 UTC

Description Evgeny Kolesnikov 2022-09-27 12:30:40 UTC
Description of problem:
Images built with image-builder on-prem using the ospp, cui & stig profiles won't boot. The issue is that these profiles enable fips mode and the images won't boot with /boot on a separate partition.

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

How reproducible:


Steps to Reproduce:
1. using osbuild-composer to build an image on-prem, create a blueprint with the following customizations:

[customizations.openscap]
profile_id = "ospp"  # or cui
datastream = "/usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml"

2. Attempt to boot the image

Actual results:
Image won't boot

Expected results:
Image boots

Additional info:
A workaround for this is to add /boot/<PARTITION> to the kernel arguments.

Upstream issue: https://github.com/ComplianceAsCode/content/issues/9559

Comment 3 Evgeny Kolesnikov 2023-04-25 10:26:00 UTC
We modified the CaC content in a way that it won't try to enable
the FIPS mode in the ImageBuilder pipeline as the result won't
FIPS-compliant due to lack of support for FIPS in IB workers.

https://github.com/ComplianceAsCode/content/pull/10245


Note You need to log in before you can comment on or make changes to this bug.