From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
David Windsor <dwindsor@gmail.com>,
SELinux <selinux@tycho.nsa.gov>
Subject: Re: I would like to change the behavior of MCS label creations in directory.
Date: Tue, 18 Oct 2011 08:34:47 -0400 [thread overview]
Message-ID: <4E9D7267.9060004@tresys.com> (raw)
In-Reply-To: <4E985BFB.1000806@redhat.com>
On 10/14/11 11:57, Daniel J Walsh wrote:
> Eric and I have come up with the following syntax for this behaviour.
>
> default_trans level dir_file_class_set parent;
I think we want this to be "range" instead of "level", since the field is actually a range.
> default_trans user dir_file_class_set process;
> default_trans role file parent;
Isn't there a better set of tokens than this? Why not make it default_user, default_role, default_type, and default_range? Creating an object doesn't really imply a transition, so "trans" seems misleading.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2011-10-18 12:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 19:53 I would like to change the behavior of MCS label creations in directory Daniel J Walsh
2011-09-22 20:13 ` Guido Trentalancia
2011-09-22 20:31 ` Stephen Smalley
2011-09-22 20:32 ` Daniel J Walsh
2011-09-22 20:37 ` Stephen Smalley
2011-09-22 20:42 ` Stephen Smalley
2011-09-23 15:01 ` Daniel J Walsh
2011-09-23 15:07 ` Stephen Smalley
2011-09-23 16:06 ` Guido Trentalancia
2011-09-23 17:33 ` Daniel J Walsh
2011-09-24 22:05 ` David Windsor
2011-09-27 16:06 ` Stephen Smalley
2011-09-27 16:50 ` David Windsor
2011-09-27 16:51 ` Stephen Smalley
2011-09-27 18:13 ` Daniel J Walsh
2011-10-14 15:57 ` Daniel J Walsh
2011-10-18 12:34 ` Christopher J. PeBenito [this message]
[not found] ` <00243337-937e-4e6b-880b-ba2f351112e7@email.android.com>
2011-10-18 22:07 ` David Windsor
2011-10-19 16:55 ` Stephen Smalley
2011-10-19 15:31 ` Joshua Brindle
2011-10-19 16:26 ` Stephen Smalley
2011-11-22 18:59 ` Eric Paris
2011-11-22 19:25 ` Stephen Smalley
2011-11-22 19:37 ` Eric Paris
2011-11-22 19:39 ` Stephen Smalley
2011-11-22 19:42 ` Eric Paris
2011-10-19 16:36 ` Kyle Moffett
2011-10-19 17:41 ` Daniel J Walsh
2011-10-19 17:47 ` Joshua Brindle
2011-10-19 17:50 ` Daniel J Walsh
2011-09-22 20:41 ` 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=4E9D7267.9060004@tresys.com \
--to=cpebenito@tresys.com \
--cc=dwalsh@redhat.com \
--cc=dwindsor@gmail.com \
--cc=sds@tycho.nsa.gov \
--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.