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.