From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 29/34]: patch to add sys_ptrace permission to the dbus module
Date: Mon, 28 Feb 2011 10:31:35 -0500 [thread overview]
Message-ID: <4D6BBFD7.4040301@redhat.com> (raw)
In-Reply-To: <4D6BB5C1.5040609@tresys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/28/2011 09:48 AM, Christopher J. PeBenito wrote:
> On 02/16/11 01:35, Guido Trentalancia wrote:
>> This patch adds self:capability sys_ptrace to the dbus module.
>>
>> --- refpolicy-git-02022011-test-apply/policy/modules/services/dbus.te 2011-02-07 02:36:05.874787818 +0100
>> +++ refpolicy-git-02022011-test-apply2/policy/modules/services/dbus.te 2011-02-07 02:51:51.910683659 +0100
>> @@ -52,7 +52,7 @@ ifdef(`enable_mls',`
>>
>> # dac_override: /var/run/dbus is owned by messagebus on Debian
>> # cjp: dac_override should probably go in a distro_debian
>> -allow system_dbusd_t self:capability { dac_override setgid setpcap setuid };
>> +allow system_dbusd_t self:capability { dac_override setgid setpcap setuid sys_ptrace };
>> dontaudit system_dbusd_t self:capability sys_tty_config;
>> allow system_dbusd_t self:process { getattr getsched signal_perms setpgid getcap setcap };
>> allow system_dbusd_t self:fifo_file rw_fifo_file_perms;
>
> I find this highly questionable. It needs justification.
>
We do not have this in Fedora. Might be similar to policykit, examining
/proc/PID/cmdline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAk1rv9cACgkQrlYvE4MpobPFbwCfS+tg0VMnAtOwN8G67WnBPN1J
xX0An1tydi5iEvayHq/QtiZPqLWtSEdf
=nXYv
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-02-28 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 6:35 [refpolicy] [PATCH 29/34]: patch to add sys_ptrace permission to the dbus module Guido Trentalancia
2011-02-28 14:48 ` Christopher J. PeBenito
2011-02-28 15:31 ` Daniel J Walsh [this message]
2011-02-28 18:30 ` Guido Trentalancia
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=4D6BBFD7.4040301@redhat.com \
--to=dwalsh@redhat.com \
--cc=refpolicy@oss.tresys.com \
/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.