Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The rule set under OpenSCAP profile 'xccdf_org.ssgproject.content_profile_pci-dss' below is checking group_id with 4 instead of 0 (root). So the rule is failing even if group_id is set as expected.
<ns4:file_state id="oval:ssg-state_rsyslog_files_groupownership:ste:1" version="1">
<ns4:type operation="equals">regular</ns4:type>
<ns4:group_id datatype="int">4</ns4:group_id> <<< ### 4 and not 0
</ns4:file_state>
<ns4:file_state id="oval:ssg-state_rsyslog_files_ownership:ste:1" version="1">
<ns4:type operation="equals">regular</ns4:type>
<ns4:user_id datatype="int">0</ns4:user_id>
Version-Release number of selected component (if applicable):
openscap-1.2.10-3.el7_3.x86_64
How reproducible:
Run the report to check group ownership on all rsyslog log files as follows.
Steps to Reproduce:
1. Install scap-security-guide package
2. Set owner and group as root.root for all rsyslog log files
3. Run rule to check group ownership of root files
Actual results:
Rule fails, as it expects group_id to be 4 instead of 0.
Expected results:
Rule should pass, as group is set as root for all the files. The rule should check group_id to be '0' and not '4'.
Additional info:
Comment 2Watson Yuuma Sato
2018-12-10 16:32:54 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, 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-2019:2198
Description of problem: The rule set under OpenSCAP profile 'xccdf_org.ssgproject.content_profile_pci-dss' below is checking group_id with 4 instead of 0 (root). So the rule is failing even if group_id is set as expected. <ns4:file_state id="oval:ssg-state_rsyslog_files_groupownership:ste:1" version="1"> <ns4:type operation="equals">regular</ns4:type> <ns4:group_id datatype="int">4</ns4:group_id> <<< ### 4 and not 0 </ns4:file_state> <ns4:file_state id="oval:ssg-state_rsyslog_files_ownership:ste:1" version="1"> <ns4:type operation="equals">regular</ns4:type> <ns4:user_id datatype="int">0</ns4:user_id> Version-Release number of selected component (if applicable): openscap-1.2.10-3.el7_3.x86_64 How reproducible: Run the report to check group ownership on all rsyslog log files as follows. Steps to Reproduce: 1. Install scap-security-guide package 2. Set owner and group as root.root for all rsyslog log files 3. Run rule to check group ownership of root files Actual results: Rule fails, as it expects group_id to be 4 instead of 0. Expected results: Rule should pass, as group is set as root for all the files. The rule should check group_id to be '0' and not '4'. Additional info: