Bug 902895 - SELinux is preventing /usr/bin/python2.7 from 'execute' accesses on the chr_file /dev/zero.
SELinux is preventing /usr/bin/python2.7 from 'execute' accesses on the chr_f...
Product: Fedora
Classification: Fedora
Component: blueman (Show other bugs)
i686 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Juan Manuel Rodriguez
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-01-22 11:28 EST by blitzter
Modified: 2013-12-09 19:26 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-12-09 19:26:44 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description blitzter 2013-01-22 11:28:52 EST
Description of problem:
SELinux is preventing /usr/bin/python2.7 from 'execute' accesses on the chr_file /dev/zero.

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

If you believe that python2.7 should be allowed execute access on the zero chr_file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
allow this access for now by executing:
# grep blueman-mechani /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:blueman_t:s0-s0:c0.c1023
Target Context                system_u:object_r:zero_device_t:s0
Target Objects                /dev/zero [ chr_file ]
Source                        blueman-mechani
Source Path                   /usr/bin/python2.7
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           python-2.7.3-13.fc18.i686
Target RPM Packages           
Policy RPM                    selinux-policy-3.11.1-67.fc18.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Permissive
Host Name                     (removed)
Platform                      Linux (removed) 3.7.2-204.fc18.i686.PAE #1 SMP Wed
                              Jan 16 16:31:26 UTC 2013 i686 i686
Alert Count                   1
First Seen                    2013-01-22 21:58:01 IST
Last Seen                     2013-01-22 21:58:01 IST
Local ID                      40547ddd-0052-45e1-9069-157c01f2d52f

Raw Audit Messages
type=AVC msg=audit(1358872081.993:327): avc:  denied  { execute } for  pid=1478 comm="blueman-mechani" path="/dev/zero" dev="devtmpfs" ino=22 scontext=system_u:system_r:blueman_t:s0-s0:c0.c1023 tcontext=system_u:object_r:zero_device_t:s0 tclass=chr_file

type=SYSCALL msg=audit(1358872081.993:327): arch=i386 syscall=mmap2 success=yes exit=-1219973120 a0=0 a1=2000 a2=7 a3=2 items=0 ppid=1477 pid=1478 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=blueman-mechani exe=/usr/bin/python2.7 subj=system_u:system_r:blueman_t:s0-s0:c0.c1023 key=(null)

Hash: blueman-mechani,blueman_t,zero_device_t,chr_file,execute


#============= blueman_t ==============
allow blueman_t zero_device_t:chr_file execute;

audit2allow -R

#============= blueman_t ==============
allow blueman_t zero_device_t:chr_file execute;

Additional info:
hashmarkername: setroubleshoot
kernel:         3.7.2-204.fc18.i686.PAE
type:           libreport
Comment 1 Daniel Walsh 2013-01-22 14:02:54 EST
Why is blueman mmap2 /dev/zero for execute?
Comment 2 Juan Manuel Rodriguez 2013-12-09 19:26:44 EST
Hello. The blueman package has been retired from Fedora. 

A new maintainer has forked blueman as the old version wasn't actively developed. You may reach the new repository at github [1], and re-file this bug if appropriate

I apologize for any issues the package has had over the time it was packaged in Fedora. If blueman gets Bluez 5 support, I'll consider repackaging it for Fedora. 


[1] https://github.com/cschramm/blueman

Note You need to log in before you can comment on or make changes to this bug.