Bug 2077531
| Summary: | Rule xccdf_org.ssgproject.content_rule_chronyd_run_as_chrony_user enforces setting "-u chrony" which is overkill | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Renaud Métrich <rmetrich> |
| Component: | scap-security-guide | Assignee: | Matěj Týč <matyc> |
| Status: | CLOSED ERRATA | QA Contact: | Milan Lysonek <mlysonek> |
| Severity: | low | Docs Contact: | Jan Fiala <jafiala> |
| Priority: | low | ||
| Version: | 8.5 | CC: | amike, ggasparb, jafiala, maburgha, matyc, mburket, mhaicman, mlysonek, wsato |
| Target Milestone: | rc | Keywords: | AutoVerified, Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | scap-security-guide-0.1.63-1.el8 | Doc Type: | Bug Fix |
| Doc Text: |
.Rules for `chronyd` do not require explicit `chrony` user configuration
RHEL runs `chronyd` under the `chrony` user by default. Previously, the check and remediation for the `chronyd` service configuration user were stricter than necessary. The overly strict check led to false positives and to excessive remediations. In this version, the check and remediations of the rule `xccdf_org.ssgproject.content_rule_chronyd_run_as_chrony_user` are updated, for both the minimalistic correct configuration and legacy explicit correct configurations pass. As a result, the rule respects the default RHEL behavior and does not require explicit `chrony` user configuration.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-11-08 09:39:56 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
Renaud Métrich
2022-04-21 14:25:36 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:7563 |