Bug 750429 - SELinux is preventing /usr/bin/tor from 'read' accesses on the directory cpu.
Summary: SELinux is preventing /usr/bin/tor from 'read' accesses on the directory cpu.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 15
Hardware: i386
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: setroubleshoot_trace_hash:3ed53e002d1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-01 05:04 UTC by Phoenix
Modified: 2011-12-04 02:38 UTC (History)
3 users (show)

Fixed In Version: selinux-policy-3.9.16-48.fc15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-04 02:38:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Phoenix 2011-11-01 05:04:52 UTC
SELinux is preventing /usr/bin/tor from 'read' accesses on the directory cpu.

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

If you believe that tor should be allowed read access on the cpu directory 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 tor /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:tor_t:s0
Target Context                system_u:object_r:sysfs_t:s0
Target Objects                cpu [ dir ]
Source                        tor
Source Path                   /usr/bin/tor
Port                          <未知>
Host                          (removed)
Source RPM Packages           tor-0.2.3.6.alpha-tor.0.rh15
Target RPM Packages           
Policy RPM                    selinux-policy-3.9.16-44.fc15
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 2.6.40.6-0.fc15.i686 #1 SMP Tue Oct
                              4 00:51:19 UTC 2011 i686 i686
Alert Count                   1
First Seen                    2011年11月01日 星期二 13时00分21秒
Last Seen                     2011年11月01日 星期二 13时00分21秒
Local ID                      ab8b8a5a-11b3-42de-8c85-e393502dff22

Raw Audit Messages
type=AVC msg=audit(1320123621.695:22): avc:  denied  { read } for  pid=1133 comm="tor" name="cpu" dev=sysfs ino=30 scontext=system_u:system_r:tor_t:s0 tcontext=system_u:object_r:sysfs_t:s0 tclass=dir


type=SYSCALL msg=audit(1320123621.695:22): arch=i386 syscall=open success=no exit=EACCES a0=4ea778ab a1=98800 a2=4eab2ff4 a3=53 items=0 ppid=1 pid=1133 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=tor exe=/usr/bin/tor subj=system_u:system_r:tor_t:s0 key=(null)

Hash: tor,tor_t,sysfs_t,dir,read

audit2allow

#============= tor_t ==============
allow tor_t sysfs_t:dir read;

audit2allow -R

#============= tor_t ==============
allow tor_t sysfs_t:dir read;

Comment 1 Miroslav Grepl 2011-11-01 12:02:07 UTC
Fixed in selinux-policy-3.9.16-46.fc15

Comment 2 Fedora Update System 2011-11-16 16:20:10 UTC
selinux-policy-3.9.16-48.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/selinux-policy-3.9.16-48.fc15

Comment 3 Fedora Update System 2011-11-17 23:38:32 UTC
Package selinux-policy-3.9.16-48.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.9.16-48.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-16023/selinux-policy-3.9.16-48.fc15
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2011-12-04 02:38:30 UTC
selinux-policy-3.9.16-48.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.


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