Bug 2129100
Summary: | After provisioning with ospp profile remediation, enable_fips_mode fails on s390x | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Jan Pazdziora (Red Hat) <jpazdziora> |
Component: | scap-security-guide | Assignee: | Vojtech Polasek <vpolasek> |
Status: | CLOSED ERRATA | QA Contact: | Milan Lysonek <mlysonek> |
Severity: | unspecified | Docs Contact: | Petr Hybl <phybl> |
Priority: | unspecified | ||
Version: | 8.6 | CC: | ggasparb, jcerny, jjaburek, jpazdziora, maburgha, matyc, mhaicman, mjahoda, mlysonek, sgrubb, vpolasek, wsato |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | scap-security-guide-0.1.69-1.el8 | Doc Type: | Bug Fix |
Doc Text: |
.The SCAP `enable_fips_mode` rule now checks only `fips=1` on 64-bit IBM Z architecture
Previously, the SCAP Security Guide rule `enable_fips_mode` did check the contents of the `/boot/grub2/grubenv` file. Consequently, the 64-bit IBM Z architecture did not use `/boot/grub2/grubenv` file for FIPS mode. With this update, the OVAL rule `enable_fips_mode` now test if argument `fips=1` for Linux kernel is present in `/boot/loader/entries/.*.conf` file on 64-bit IBM Z architecture.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2023-11-14 15:36:38 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1940119 |
Description
Jan Pazdziora (Red Hat)
2022-09-22 14:00:32 UTC
I believe the problem comes from oval:ssg-test_grubenv_fips_mode:tst:1 which should not be present for non-grub environments like s390x. *** Bug 2185882 has been marked as a duplicate of this bug. *** Fix is merged in Upstream: https://github.com/ComplianceAsCode/content/pull/10897 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 (scap-security-guide bug fix 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-2023:7056 |