Bug 339941

Summary: AVC denial on manual X launch
Product: [Fedora] Fedora Reporter: Warren Togami <wtogami>
Component: selinux-policyAssignee: Daniel Walsh <dwalsh>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: ajax
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Current Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-01-30 19:19:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Warren Togami 2007-10-19 15:56:02 UTC
Below is a common usage of X that thin client users might do.  Is there any safe
rule that could allow this by default?

X -query localhost :1 
type=AVC msg=audit(1192652597.024:122): avc:  denied  { read } for  pid=7979
comm="X" name=".X1-lock" dev=dm-3 ino=2098934
scontext=root:system_r:xdm_xserver_t:s0-s0:c0.c1023
tcontext=system_u:object_r:unconfined_tmp_t:s0 tclass=file
type=AVC msg=audit(1192652597.024:123): avc:  denied  { unlink } for  pid=7979
comm="X" name=".X1-lock" dev=dm-3 ino=2098934
scontext=root:system_r:xdm_xserver_t:s0-s0:c0.c1023
tcontext=system_u:object_r:unconfined_tmp_t:s0 tclass=file

Comment 1 Daniel Walsh 2007-10-19 18:09:20 UTC
The question I have is why is this using /tmp at all.  X is supposed to be using
the virtual sockets so why is it creating a lock file in /tmp?

Comment 2 Daniel Walsh 2007-10-22 14:07:02 UTC
Fixed in selinux-policy-3.0.8-29.fc8.src.rpm


Comment 3 Daniel Walsh 2008-01-30 19:19:14 UTC
Bulk closing all bugs in Fedora updates in the modified state.  If you bug is
not fixed, please reopen.