From: Darrel Goeddel <dgoeddel@TrustedCS.com>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
selinux <selinux@tycho.nsa.gov>,
selinux-dev@tresys.com
Subject: Re: policy hierarchy patch
Date: Thu, 07 Apr 2005 16:29:19 -0500 [thread overview]
Message-ID: <4255A62F.80405@trustedcs.com> (raw)
In-Reply-To: <1112907833.19565.9.camel@localhost>
Joshua Brindle wrote:
> On Thu, 2005-04-07 at 11:30 -0500, Darrel Goeddel wrote:
>
>>Stephen Smalley wrote:
>>>The original hierarchy patch also collapsed the identifier and
>>>user_identifier together, thereby allowing "-" to occur in any
>>>identifier. As a result, if someone specifies s0-s9 in the policy
>>>without whitespace, it will be incorrectly interpreted as an attempt to
>>>specify a level named "s0-s9". Further, nothing prevents someone from
>>>defining a level or category name that includes a "-" presently.
>>>Options are to revert the change from the original patch that collapsed
>>>identifier and user_identifier together (only adding "." to identifier,
>>>not "-") or to add further handling to the action routines to deal with
>>>it.
>>>
>
>
> Out of curiousity, why are sensitivity ranged specified with '-' and
> category ranged specified with '.'?
>
To ease (or make possible) parsing things like "s0:c1 . c4 - s1:c1 . c4".
If it was "s0:c1 - c4 - s1:c1 - c4", the second '-' is ambiguous. At least
thats why I think its that way...
> I think this is correct, not just because of the explanation above but
> because this may cause issues with space sensitivity in type sets, ie
> { foo-bar } is the same as { foo -bar } now, but wouldn't be with this
> patch. I'll fix this and send out a patch tomorrow.
Ahhh. I misread the comment earlier - I read it as "go back to IDENTIFIER and
MLS_IDENTIFIER". I think going back to "USER_IDENTIFIER and IDENTIFIER", and
ditching the '-' in Ithe current DENTIFIER is the way to go.
--
Darrel
--
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:[~2005-04-07 21:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 16:14 policy hierarchy patch Joshua Brindle
2005-04-04 17:24 ` Stephen Smalley
2005-04-04 19:37 ` Joshua Brindle
2005-04-04 22:05 ` Darrel Goeddel
2005-04-05 14:03 ` Joshua Brindle
2005-04-05 23:35 ` Darrel Goeddel
2005-04-06 21:38 ` Darrel Goeddel
2005-04-07 12:32 ` Stephen Smalley
2005-04-07 16:30 ` Darrel Goeddel
2005-04-07 21:03 ` Joshua Brindle
2005-04-07 21:29 ` Darrel Goeddel [this message]
2005-04-08 18:26 ` Joshua Brindle
2005-04-11 20:39 ` Darrel Goeddel
2005-04-14 13:01 ` Stephen Smalley
2005-04-13 16:16 ` Stephen Smalley
2005-04-13 16:46 ` Stephen Smalley
[not found] ` <200504221152.39180.russell@coker.com.au>
2005-04-22 12:32 ` Joshua Brindle
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=4255A62F.80405@trustedcs.com \
--to=dgoeddel@trustedcs.com \
--cc=jbrindle@tresys.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux-dev@tresys.com \
--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.