Bug 2129100
| Summary: | After provisioning with ospp profile remediation, enable_fips_mode fails on s390x | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Jan Pazdziora <jpazdziora> |
| Component: | scap-security-guide | Assignee: | Vojtech Polasek <vpolasek> |
| Status: | MODIFIED --- | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.6 | CC: | ggasparb, jcerny, jjaburek, jpazdziora, maburgha, matyc, mhaicman, 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: |
.Fixed rule enable_fips_mode on s390x architecture
The OVAL check in rule `enable_fips_mode` has been fixed to work correctly on the s390x architecture.
The check will not check the contents of `/boot/grub2/grubenv` file which isn't relevant on the 390x architecture
because on this architecture the GRUB bootloader isn't used. On the s390x architecture, only a test if argument `fips=1` for Linux kernel is present in `/boot/loader/entries/.*.conf` files is checked.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 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
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 |