From: Martin Orr <martin@martinorr.name>
To: SELinux List <selinux@tycho.nsa.gov>,
"Christopher J. PeBenito" <cpebenito@tresys.com>
Subject: [refpolicy] Let dpkg scripts ptrace
Date: Wed, 25 Jun 2008 17:31:31 +0100 [thread overview]
Message-ID: <486272E3.109@martinorr.name> (raw)
[-- Attachment #1: Type: text/plain, Size: 331 bytes --]
Some dpkg maintainer scripts run pidof, which needs the sys_ptrace capability.
Mar 17 15:14:31 caligula kernel: audit(1205766871.788:13): avc: denied {
sys_ptrace } for pid=4214 comm="pidof" capability=19
scontext=system_u:system_r:dpkg_script_t:s0
tcontext=system_u:system_r:dpkg_script_t:s0 tclass=capability
--
Martin Orr
[-- Attachment #2: 118_dpkg_script_pidof --]
[-- Type: text/plain, Size: 1035 bytes --]
Written by: Martin Orr
Allow dpkg scripts to run pidof
Mar 17 15:14:31 caligula kernel: audit(1205766871.788:13): avc: denied { sys_ptrace } for pid=4214 comm="pidof" capability=19 scontext=system_u:system_r:dpkg_script_t:s0 tcontext=system_u:system_r:dpkg_script_t:s0 tclass=capability
Index: policy/modules/admin/dpkg.te
===================================================================
--- policy/modules/admin/dpkg.te.orig
+++ policy/modules/admin/dpkg.te
@@ -216,7 +216,7 @@
#
# TODO: actually use dpkg_script_t
-allow dpkg_script_t self:capability { chown dac_override dac_read_search fowner fsetid setgid setuid ipc_lock sys_chroot sys_nice mknod kill };
+allow dpkg_script_t self:capability { chown dac_override dac_read_search fowner fsetid setgid setuid ipc_lock sys_chroot sys_nice mknod kill sys_ptrace };
allow dpkg_script_t self:process ~{ ptrace setcurrent setexec setfscreate setrlimit execmem execstack execheap };
allow dpkg_script_t self:fd use;
allow dpkg_script_t self:fifo_file rw_fifo_file_perms;
next reply other threads:[~2008-06-25 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 16:31 Martin Orr [this message]
2008-07-18 13:54 ` [refpolicy] Let dpkg scripts ptrace Christopher J. PeBenito
2008-08-07 14:48 ` Martin Orr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=486272E3.109@martinorr.name \
--to=martin@martinorr.name \
--cc=cpebenito@tresys.com \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.