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: Mon, 04 Apr 2005 17:05:18 -0500 [thread overview]
Message-ID: <4251BA1E.9040406@trustedcs.com> (raw)
In-Reply-To: <1112643447.19527.30.camel@localhost>
Joshua Brindle wrote:
> Yes you appear to be right. It turns out that this is a hard problem,
> currently '.' is treated as a terminal some of the time and part of an
> identifier other times. We tried to fix this problem by using lex start
> states to disambiguate mls identifiers and normal ones but this became
> problematic in contexts. Namely the following is currently valid:
>
> user:role:type:s0-s9:cat1. cat2
>
> note the space, now currently parts of the language require 2 contexts
> in 1 rule, specifically netifcon:
>
> netifcon user:role:type:s0:cat1 user:role:type:s1:cat1
>
> If the context were always the last thing on the line we could end the
> lex start state but since that isn't the case the yacc lookahead causes
> the next identifier to be treated as an mls_identifier.
>
> I said all that to ask if it is feasible to combine identifier and
> mls_identifier in the patch and remove the terminal '.'. This would
> cause category ranges to be 1 identifier and they'd have to be split
> manually but otherwise it should work. The only visible change would be
> that spaces would no longer be allowed between the category and the '.'.
>
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.
--
Darrel (Go Illini!)
--
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-04 22:05 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 [this message]
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
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=4251BA1E.9040406@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.