Bug 1022214

Summary: SELinux is preventing /usr/lib64/xulrunner/plugin-container from 'name_connect' accesses on the tcp_socket .
Product: [Fedora] Fedora Reporter: Andrig Miller <andrig.t.miller>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: akostadi, dominick.grift, dwalsh, lvrabec, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:2580d7a4c3d40edb20088f0a1970e640a34423d6dae9c899988117ca29c58a20
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-22 17:59:24 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 Andrig Miller 2013-10-22 17:31:21 UTC
Description of problem:
I joined a redhat Blue Jeans test video conference call.

redhat.bluejeans.com
SELinux is preventing /usr/lib64/xulrunner/plugin-container from 'name_connect' accesses on the tcp_socket .

*****  Plugin mozplugger (89.7 confidence) suggests  *************************

If you want to use the plugin package
Then you must turn off SELinux controls on the Firefox plugins.
Do
# setsebool -P unconfined_mozilla_plugin_transition 0

*****  Plugin catchall_boolean (10.0 confidence) suggests  *******************

If you want to allow mozilla plugin domain to connect to the network using TCP.
Then you must tell SELinux about this by enabling the 'mozilla_plugin_can_network_connect' boolean.
You can read 'mozilla_selinux' man page for more details.
Do
setsebool -P mozilla_plugin_can_network_connect 1

*****  Plugin catchall (1.69 confidence) suggests  ***************************

If you believe that plugin-container should be allowed name_connect access on the  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 plugin-containe /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c
                              0.c1023
Target Context                system_u:object_r:commplex_main_port_t:s0
Target Objects                 [ tcp_socket ]
Source                        plugin-containe
Source Path                   /usr/lib64/xulrunner/plugin-container
Port                          5000
Host                          (removed)
Source RPM Packages           xulrunner-24.0-2.fc19.x86_64
Target RPM Packages           
Policy RPM                    selinux-policy-3.12.1-74.10.fc19.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 3.11.4-201.fc19.x86_64 #1 SMP Thu
                              Oct 10 14:11:18 UTC 2013 x86_64 x86_64
Alert Count                   12
First Seen                    2013-10-10 07:06:54 MDT
Last Seen                     2013-10-22 11:29:38 MDT
Local ID                      f1688fa7-9fed-48f4-ba74-2c4a9c424d2e

Raw Audit Messages
type=AVC msg=audit(1382462978.563:131): avc:  denied  { name_connect } for  pid=18981 comm="plugin-containe" dest=5000 scontext=unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c0.c1023 tcontext=system_u:object_r:commplex_main_port_t:s0 tclass=tcp_socket


type=SYSCALL msg=audit(1382462978.563:131): arch=x86_64 syscall=connect success=no exit=EACCES a0=3a a1=7fdd89d2455c a2=10 a3=7fdd8d2f46f0 items=0 ppid=1873 pid=18981 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 ses=1 tty=(none) comm=plugin-containe exe=/usr/lib64/xulrunner/plugin-container subj=unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c0.c1023 key=(null)

Hash: plugin-containe,mozilla_plugin_t,commplex_main_port_t,tcp_socket,name_connect

Additional info:
reporter:       libreport-2.1.8
hashmarkername: setroubleshoot
kernel:         3.11.4-201.fc19.x86_64
type:           libreport

Comment 1 Daniel Walsh 2013-10-22 17:59:24 UTC
*****  Plugin catchall_boolean (10.0 confidence) suggests  *******************

If you want to allow mozilla plugin domain to connect to the network using TCP.
Then you must tell SELinux about this by enabling the 'mozilla_plugin_can_network_connect' boolean.
You can read 'mozilla_selinux' man page for more details.
Do
setsebool -P mozilla_plugin_can_network_connect 1


Alert told you what to do.

Comment 2 Aleksandar Kostadinov 2015-03-19 08:25:39 UTC
for bluejeans selinux switch see bug 1110355