From: Paul Moore <paul.moore@hp.com>
To: Joshua Brindle <method@manicmethod.com>
Cc: SE Linux <selinux@tycho.nsa.gov>, Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: releasibility in mcstransd
Date: Mon, 9 Jun 2008 16:50:59 -0400 [thread overview]
Message-ID: <200806091650.59271.paul.moore@hp.com> (raw)
In-Reply-To: <484D91BB.3080904@manicmethod.com>
On Monday 09 June 2008 4:25:31 pm Joshua Brindle wrote:
> I am adding releasibility support to mcstransd and just wanted to see
> if there were any comments or complaints to what I'm planning here.
>
> Rather than adding a generic prefix mechanism like the CMW encodings
> I did something specific for releasibility, in setrans.conf:
>
> releasibility c100.c128
>
> then encodings look like:
>
> s0:~c100 = rel_US
> s0:~c101 = rel_Texas
>
> so a file with s0:c102.c128 would translate to s0:rel_US,rel_Texas.
>
> any comments? Does anyone think this is absolutely the wrong
> approach?
Unless there is a reason to do away with the existing CMW convention I
think we should probably stick with it for no other reason than it is
familiar to users migrating from CMW boxes to SELinux.
--
paul moore
linux @ hp
--
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:[~2008-06-09 20:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 20:25 releasibility in mcstransd Joshua Brindle
2008-06-09 20:50 ` Paul Moore [this message]
2008-06-09 21:04 ` Chad Hanson
2008-06-11 3:04 ` Joe Nall
2008-06-11 14:11 ` Daniel J Walsh
2008-06-20 15:37 ` Joshua Brindle
2008-06-20 18:14 ` Joe Nall
2008-06-20 18:26 ` Joshua Brindle
2008-06-20 18:34 ` Joe Nall
2008-06-27 11:51 ` Daniel J Walsh
2008-06-27 13:42 ` Joshua Brindle
2008-06-27 18:41 ` Paul Moore
2008-06-27 18:56 ` Joshua Brindle
2008-07-08 15:54 ` Joe Nall
2008-07-08 17:11 ` Stephen Smalley
2008-07-08 17:22 ` Joshua Brindle
2008-06-20 18:41 ` Joe Nall
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=200806091650.59271.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=method@manicmethod.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.