From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] roles_staff.patch
Date: Tue, 06 Jul 2010 08:42:28 -0400 [thread overview]
Message-ID: <4C3324B4.9030603@tresys.com> (raw)
In-Reply-To: <4C06BF9E.6030300@redhat.com>
On 06/02/10 16:31, Daniel J Walsh wrote:
> http://people.fedoraproject.org/~dwalsh/SELinux/F14/roles_staff.patch
>
> Allow staff user to exec files on removable devices
>
> Needs access to run sandbox
>
> Additional access for staff reading kernel info.
>
> staff_t needs to run newrole to relabel content in his homedir
>
> Needs to run ping
>
> Added distro_redhat to eliminate all of the transitions that we did not
> want.
This needs to be cleaned up, its way off from typical refpolicy style.
Also, instead of ifndef'ing individual optional blocks, they should all
be collected into one big ifndef block.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2010-07-06 12:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 20:31 [refpolicy] roles_staff.patch Daniel J Walsh
2010-07-06 12:42 ` Christopher J. PeBenito [this message]
2010-07-12 14:19 ` Daniel J Walsh
2010-07-19 17:28 ` Christopher J. PeBenito
2010-07-20 18:40 ` Daniel J Walsh
-- strict thread matches above, loose matches on Subject: below --
2010-08-26 22:32 Daniel J Walsh
2010-02-17 15:54 Daniel J Walsh
2010-02-18 16:32 ` Christopher J. PeBenito
2010-02-18 17:57 ` Daniel J Walsh
2010-02-19 13:47 ` Christopher J. PeBenito
2009-11-12 21:07 Daniel J Walsh
2010-02-17 14:05 ` Christopher J. PeBenito
2009-05-21 15:35 Daniel J Walsh
2009-03-05 16:26 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=4C3324B4.9030603@tresys.com \
--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.