Bug 1811215

Summary: /run/dbus permissions in the packa do not match the real ones
Product: Red Hat Enterprise Linux 8 Reporter: Carlos Santos <casantos>
Component: dbusAssignee: David King <dking>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 8.1   
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-18 09:49:52 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 Carlos Santos 2020-03-06 21:12:13 UTC
Description of problem:

Customer is trying to comply with the Draft RHEL 8 STIG, which states that
"the default file permissions, ownership, and group membership of system files
and commands must match the vendor values." to comply with NIST 800-53r4 AU-9
and AC-3.

The RPM permissions for the /run/dbus directory are not the same as the
permssions for the file on the file system.

Version-Release number of selected component (if applicable):

dbus-daemon-1.12.8-9.el8.x86_64

How reproducible:

Always

Steps to Reproduce:
1. rpm -qlv dbus-daemon |grep -F /run/dbus
2. ls -ld /run/dbus

Actual results:

rpm -qlv dbus-daemon |grep -F /run/dbus
d---------    2 root    root                        0 Aug  1  2019 /run/dbus

$ ls -ld /run/dbus
drwxr-xr-x. 2 root root 60 Feb 16 19:04 /run/dbus

Expected results:

rpm -qlv dbus-daemon |grep -F /run/dbus
drwxr-xr-x    2 root    root                        0 Aug  1  2019 /run/dbus

$ ls -ld /run/dbus
drwxr-xr-x. 2 root root 60 Feb 16 19:04 /run/dbus

Additional info:

The bug is harmless because /run is a tmpfs which is populated by systemd and
other daemos as they run. The problem is that it makes the compliance checking
fail:

    https://github.com/ComplianceAsCode/content/issues/4802

Comment 1 David King 2020-03-18 09:49:52 UTC

*** This bug has been marked as a duplicate of bug 1797833 ***