Bug 789715 - ptrace change appears to need more exceptions.
Summary: ptrace change appears to need more exceptions.
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-12 14:30 UTC by Bruno Wolff III
Modified: 2012-02-14 20:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-14 20:49:00 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Bruno Wolff III 2012-02-12 14:30:48 UTC 
Description of problem:
Several packages are using the ptrace capability and generate lots of logs. In enforcing mode this was even blocking semodule for loading a module.

For now I am using the following:
#============= consolekit_t ==============
allow consolekit_t self:capability sys_ptrace;

#============= rtkit_daemon_t ==============
allow rtkit_daemon_t self:capability sys_ptrace;

#============= syslogd_t ==============
allow syslogd_t self:capability sys_ptrace;


Version-Release number of selected component (if applicable):
selinux-policy-targeted-3.10.0-86.fc17.noarch

Additional info:
Note that this is in rawhide. The same package works OK in branched (f17).

getsebool reports:
deny_ptrace --> off
Comment 1 Bruno Wolff III 2012-02-12 15:48:05 UTC 
It's possible that the part of the issue getting semodule to load a policy may have been just very slow do to all of the AVCs rather than actual blocking. I waited several minutes and then tried setenforce 0 and it finished shortly afterwards. But that might have been a coincidence or maybe the load was reduced a bit.
Comment 2 Daniel Walsh 2012-02-14 20:49:00 UTC 
The sys_ptrace access will be allowed in selinux-policy-3.10.0-88.fc17.noarch
Note You need to log in before you can comment on or make changes to this bug.