From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] services_snmp.patch
Date: Wed, 03 Dec 2008 10:32:19 -0500 [thread overview]
Message-ID: <1228318344.9691.547.camel@gorn> (raw)
In-Reply-To: <492C6CBB.5050806@redhat.com>
On Tue, 2008-11-25 at 16:23 -0500, Daniel J Walsh wrote:
> http://people.fedoraproject.org/~dwalsh/SELinux/F11/services_snmp.patch
>
> Add initrc labeling support
>
> /var/agentx needs a label
>
> Clean up admin interface
>
> snmp needs getsched, setsched
>
> needs ipc_lock and sys_ptrace
These two caps came up earlier this week; it makes me wonder if there is
any similarity (does it fit into a pattern?). The other one had kill
(was already on snmpd_t), sys_ptrace, and ipc_lock too. Snmpd doesn't
have process ptrace or process sigkill perms, which is why this seems
questionable.
> Reads file systems and rw xen state
>
> Dontaudit ptrace domains
>
> Checks all executables
>
> Does walks of the file systems
>
> Execs consoletype,
>
> Communicates with virtual machines and xen machines
I put the kernel_*_xen_state() calls in with the other xen_*() calls.
Merged with some other tweaks.
--
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150
next prev parent reply other threads:[~2008-12-03 15:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 21:23 [refpolicy] services_snmp.patch Daniel J Walsh
2008-12-03 15:32 ` Christopher J. PeBenito [this message]
2008-12-03 23:09 ` Daniel J Walsh
2008-12-04 13:07 ` Christopher J. PeBenito
2008-12-04 19:21 ` Daniel J Walsh
2008-12-04 19:26 ` Christopher J. PeBenito
2008-12-04 19:30 ` Daniel J Walsh
-- strict thread matches above, loose matches on Subject: below --
2010-08-26 22:21 Daniel J Walsh
2010-02-23 20:58 Daniel J Walsh
2009-11-12 22:00 Daniel J Walsh
2010-01-07 14:01 ` Christopher J. PeBenito
2009-03-05 17:04 Daniel J Walsh
2009-05-14 15:15 ` Christopher J. PeBenito
2008-10-14 19:33 Daniel J Walsh
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=1228318344.9691.547.camel@gorn \
--to=cpebenito@tresys.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.