Bug 1514273

Summary: /var/run/gdm is created with the incorrect mode
Product: Red Hat Enterprise Linux 7 Reporter: jcastran
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.4   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-17 15:29:40 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 jcastran 2017-11-16 23:42:51 UTC
Description of problem:
gdm creates /var/run/gdm/ directory within tmpfs. When the system reboots, this directory is removed and re-created. The second time it is created it is affected by umask which doesn't match what the rpm set for the directory permission.

This matters for openscap profiles, such as STIG (which we ship), that look into "rpm -Va" output and will FAIL due to incorrect mode. 

   # rpm --setperms gdm
   # rpm -V gdm
       <No results>
   # reboot
   # rpm -V gdm
       .M.......    /var/run/gdm


How reproducible:
 Easily

Steps to Reproduce:
1. Install gdm
2. Restart the system
3. rpm -V gdm

Actual results:
 # rpm -V gdm
    .M.......    /var/run/gdm

Expected results:
 # rpm -V gdm  #Nothing returned

Additional info:
   This is the same scenario as https://bugzilla.redhat.com/show_bug.cgi?id=1462802

   I would worry this may continue to happen with every package that sets files in /var/run with permissions that do not match default umask

Comment 2 jcastran 2017-11-16 23:55:59 UTC
** Correction **

Actual results:
 # rpm -V gdm
    .M....G..    /var/log/gdm

Comment 3 Ray Strode [halfline] 2017-11-17 15:29:40 UTC

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