Bug 1776780
Summary: | Rule 'xccdf_org.ssgproject.content_rule_dconf_gnome_login_banner_text' fail to remediate | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | amitkuma |
Component: | scap-security-guide | Assignee: | Watson Yuuma Sato <wsato> |
Status: | CLOSED ERRATA | QA Contact: | Gabriel Gaspar Becker <ggasparb> |
Severity: | medium | Docs Contact: | Jan Fiala <jafiala> |
Priority: | high | ||
Version: | 7.0 | CC: | ggasparb, jafiala, lcervako, matyc, mhaicman, mjahoda, openscap-maint, wsato |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | scap-security-guide-0.1.49-2.el7 | Doc Type: | Bug Fix |
Doc Text: |
.`dconf_gnome_login_banner_text` no longer incorrectly fails
Remediation of the `dconf_gnome_login_banner_text` rule in the `scap-security-guide` packages previously failed after a failure to scan the configuration. As a consequence, the remediation could not properly update the login banner configuration, which was inconsistent with expected results. With this update, Bash and Ansible remediations are more reliable and align with the configuration check implemented using the OVAL standard. As a consequence, remediations now work properly and the rule passes after remediation.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-09-29 19:52:12 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: |
Comment 13
Watson Yuuma Sato
2020-03-16 08:36:37 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-2020:3909 |