Bug 698951

Summary: SELinux is preventing /usr/lib64/xulrunner-1.9.2/mozilla-xremote-client from 'name_connect' accesses on the tcp_socket port 6000.
Product: [Fedora] Fedora Reporter: Harish Pillay <h.pillay>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 14CC: dwalsh, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: setroubleshoot_trace_hash:197665eeeef5e2f32c2d9cb02a6aee66be80e5e1784938e4f67237998de1e80a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-07 19:36:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Harish Pillay 2011-04-22 12:07:55 UTC
SELinux is preventing /usr/lib64/xulrunner-1.9.2/mozilla-xremote-client from 'name_connect' accesses on the tcp_socket port 6000.

*****  Plugin catchall (100. confidence) suggests  ***************************

If you believe that mozilla-xremote-client should be allowed name_connect access on the port 6000 tcp_socket by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep mozilla-xremote /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                unconfined_u:unconfined_r:sandbox_web_t:s0:c28,c10
                              1
Target Context                system_u:object_r:xserver_port_t:s0
Target Objects                port 6000 [ tcp_socket ]
Source                        mozilla-xremote
Source Path                   /usr/lib64/xulrunner-1.9.2/mozilla-xremote-client
Port                          6000
Host                          (removed)
Source RPM Packages           firefox-3.6.16-1.fc14
Target RPM Packages           
Policy RPM                    selinux-policy-3.9.7-37.fc14
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed)
                              2.6.35.12-88.fc14.x86_64 #1 SMP Thu Mar 31
                              21:21:57 UTC 2011 x86_64 x86_64
Alert Count                   5
First Seen                    Fri 22 Apr 2011 08:04:23 PM SGT
Last Seen                     Fri 22 Apr 2011 08:04:24 PM SGT
Local ID                      60335c76-a32c-4d0e-bf00-c1d66ae40d48

Raw Audit Messages
type=AVC msg=audit(1303473864.568:30153): avc:  denied  { name_connect } for  pid=23864 comm="firefox" dest=6000 scontext=unconfined_u:unconfined_r:sandbox_web_t:s0:c28,c101 tcontext=system_u:object_r:xserver_port_t:s0 tclass=tcp_socket


type=SYSCALL msg=audit(1303473864.568:30153): arch=x86_64 syscall=connect success=no exit=EACCES a0=3 a1=7fc322e8baf0 a2=10 a3=7fff86eff588 items=0 ppid=23677 pid=23864 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500 sgid=500 fsgid=500 tty=(none) ses=1 comm=firefox exe=/usr/lib64/firefox-3.6/firefox subj=unconfined_u:unconfined_r:sandbox_web_t:s0:c28,c101 key=(null)

Hash: mozilla-xremote,sandbox_web_t,xserver_port_t,tcp_socket,name_connect

audit2allow

#============= sandbox_web_t ==============
#!!!! This avc is allowed in the current policy

allow sandbox_web_t xserver_port_t:tcp_socket name_connect;

audit2allow -R

#============= sandbox_web_t ==============
#!!!! This avc is allowed in the current policy

allow sandbox_web_t xserver_port_t:tcp_socket name_connect;

Comment 1 Harish Pillay 2011-04-22 12:17:11 UTC
This was an experimental test of running a sandbox on my F14 machine.  I have enabled it via the command line and am not sure if this is something that needs to be become a default in the policy files.

Comment 2 Daniel Walsh 2011-04-22 12:31:23 UTC
Did it start up?

Comment 3 Harish Pillay 2011-04-22 12:44:45 UTC
yes it did, but because i started it in my usual home dir, with the following command:

sandbox -t sandbox_web_t -- /usr/bin/firefox

it was not able to get a profile setup etc. so, I did not proceed further.

Comment 4 Daniel Walsh 2011-04-22 13:06:44 UTC
Are you fully yum updated?

policycoreutils-2.0.85-30.fc14


Is your homedir mounted on NFS?