Bug 2014485
Summary: | Rebase scap-security-guide in Red Hat Enterprise Linux 8.6 to the latest upstream version | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Matěj Týč <matyc> |
Component: | scap-security-guide | Assignee: | Vojtech Polasek <vpolasek> |
Status: | CLOSED ERRATA | QA Contact: | Matus Marhefka <mmarhefk> |
Severity: | medium | Docs Contact: | Jan Fiala <jafiala> |
Priority: | unspecified | ||
Version: | 8.6 | CC: | ggasparb, jafiala, mhaicman, mlysonek, vpolasek, wsato |
Target Milestone: | rc | Keywords: | Rebase, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | scap-security-guide-0.1.60-6.el8 | Doc Type: | Enhancement |
Doc Text: |
.SCAP Security Guide rebased to 0.1.60
The SCAP Security Guide (SSG) packages have been rebased to upstream version 0.1.60. This version provides various enhancements and bug fixes, most notably:
* Rules hardening the PAM stack now use `authselect` as the configuration tool.
* Tailoring files that define profiles which represent the differences between DISA STIG automated SCAP content and SCAP automated content (delta tailoring) are now supported.
* The rule `xccdf_org.ssgproject.content_enable_fips_mode` now checks only whether the FIPS mode has been enabled properly. It does not guarantee that system components have undergone FIPS certification.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2022-05-10 14:15:29 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
Matěj Týč
2021-10-15 11:38:35 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 (scap-security-guide 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-2022:1900 |