From: Joshua Brindle <jbrindle@tresys.com>
To: Darrel Goeddel <dgoeddel@TrustedCS.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
selinux <selinux@tycho.nsa.gov>,
selinux-dev@tresys.com
Subject: Re: policy hierarchy patch
Date: Tue, 05 Apr 2005 10:03:02 -0400 [thread overview]
Message-ID: <1112709782.19531.39.camel@localhost> (raw)
In-Reply-To: <4251BA1E.9040406@trustedcs.com>
> Sounds good to me. I should actually be able to take a look at it tomorrow and
> help you out with the code. I know that the parsing isn't the prettiest... I
> think I may be able to make it look better in C code. And we didn't really like
> the spaces anyway.
>
So what were you thinking? the hierarchy stuff already has the
infrastructure for checking for '.' in the identifier and splitting out
the "parent", which in your case would be the lower part of the range.
Obviously these have hierarchy specific names and would be very
confusing to on-lookers so maybe we could generalize those to avoid
repeating code.
Then we just convert everything to identifier and anything that expects
a category can check for '.' and set the values appropriately, this
seems even cleaner than the way it's done now with the MLS_CAT_RANGE
string..
I can probably bang this out pretty quickly unless you had something
else you wanted to do with MLS or prefer to deal with that part
yourself, let me know what you want to do. Also, will you be able to
send a policy patch at the same time that rids the policy of those
spaces?
Thanks, Joshua Brindle
--
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-05 14:03 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 [this message]
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
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=1112709782.19531.39.camel@localhost \
--to=jbrindle@tresys.com \
--cc=dgoeddel@TrustedCS.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.