Bug 2192893
| Summary: | ".include =" in rhel8-playbook-stig.yml causing STIG to flag it. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Vojtech Polasek <vpolasek> |
| Component: | scap-security-guide | Assignee: | Vojtech Polasek <vpolasek> |
| Status: | CLOSED ERRATA | QA Contact: | Milan Lysonek <mlysonek> |
| Severity: | medium | Docs Contact: | Mirek Jahoda <mjahoda> |
| Priority: | medium | ||
| Version: | 8.8 | CC: | ggasparb, jcerny, jjaburek, jwright, matyc, mhaicman, mjahoda, mlysonek, openscap-maint, qe-baseos-security, smahanga, vpolasek, wsato |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | scap-security-guide-0.1.69-1.el8 | Doc Type: | Bug Fix |
| Doc Text: |
.SSG remediations are now aligned with `configure_openssl_cryptopolicy`
Previously, the SCAP Security Guide (SSG) remediation added the `=` character to the `opensslcnf.config` file. This syntax dit not match the description of the `configure_openssl_cryptopolicy` rule. Consequently, compliance checks might fail after remediations that inserted `.include =` instead of `.include` to `opensslcnf.config`. With this release, the remediation scripts are aligned with the rule description, and SSG remediations that use `configure_openssl_cryptopolicy` no longer fail due to additional `=`.
|
Story Points: | --- |
| Clone Of: | 2164995 | 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: | 2164995 | ||
| Bug Blocks: | |||
|
Comment 1
Jan Černý
2023-07-27 13:41:45 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 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 |