From: James Carter <jwcart2@tycho.nsa.gov>
To: Richard Haines <richard_c_haines@btinternet.com>
Cc: Steve Lawrence <slawrence@tresys.com>,
Dominick Grift <dominick.grift@gmail.com>,
SELinux List <selinux@tycho.nsa.gov>
Subject: Re: Update to CIL
Date: Mon, 21 Oct 2013 15:14:08 -0400 [thread overview]
Message-ID: <52657D00.5070903@tycho.nsa.gov> (raw)
In-Reply-To: <1382199839.82880.YahooMailNeo@web87903.mail.ir2.yahoo.com>
On 10/19/2013 12:23 PM, Richard Haines wrote:
> Thanks for the update. I added the fix used by Dominick and tested the various
> fixes that are now okay. However (sorry) but one new bug has been introduced
> and some others are still present:
>
> 1) New bug - I've been using tunables to select the different levels of
> support between Tresys and NSA compilers. Since this update, mapping
> inside tunables does not work (but only when using classpermissionset).
> The "tunable-mapping-error.cil" module demos this error.
>
I have noticed a problem with constraints in tunables not showing up as well.
> 2) classmapping only takes the first entry whether in a boolean or not. The
> "map-perm-error.cil" module demos this error. The Tresys compiler has
> a different problem - see text in "map-perm-error.cil".
>
I did know about this. We are going to be making some changes to classmappings
and classpermissionsets, so this will be taken care of soon.
> 3) Fails to resolve neverallow "*". The "neverallow-STAR.cil" module demos
> this error.
>
The "*" is currently seen to be an expression in CIL rather than as the name of
a set that includes all types. We are making some changes to expression and list
handling, so this could change. We have also been taking a look at using "all"
instead of "*" (since we use names instead of symbols elsewhere in CIL).
At any rate, currently you would have to define a typeattributeset and use that
in the neverallow.
Thanks for your help.
--
James Carter <jwcart2@tycho.nsa.gov>
National Security Agency
--
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:[~2013-10-21 19:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 18:20 Update to CIL James Carter
2013-10-18 20:02 ` Dominick Grift
2013-10-19 13:32 ` Dominick Grift
2013-10-19 18:03 ` Dominick Grift
2013-10-20 14:25 ` Dominick Grift
2013-10-21 13:25 ` Steve Lawrence
2013-10-21 18:56 ` James Carter
2013-10-21 12:35 ` Steve Lawrence
2013-10-19 16:23 ` Richard Haines
2013-10-21 13:36 ` Steve Lawrence
2013-10-21 14:22 ` Richard Haines
2013-10-21 14:46 ` Steve Lawrence
2013-10-21 15:49 ` Request for a new CIL statement Richard Haines
2013-10-21 19:14 ` James Carter [this message]
2013-10-23 13:59 ` Update to CIL Dominick Grift
2013-10-23 14:29 ` James Carter
2013-10-23 15:15 ` Dominick Grift
2013-10-23 15:58 ` James Carter
2013-10-23 17:00 ` James Carter
2013-10-23 17:27 ` Dominick Grift
2013-10-24 20:16 ` Dominick Grift
2013-10-25 17:53 ` Dominick Grift
2013-10-25 18:40 ` James Carter
2013-10-25 18:55 ` Dominick Grift
2013-10-25 18:40 ` Dominick Grift
2013-10-26 11:58 ` Dominick Grift
2013-10-31 9:45 ` Dominick Grift
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=52657D00.5070903@tycho.nsa.gov \
--to=jwcart2@tycho.nsa.gov \
--cc=dominick.grift@gmail.com \
--cc=richard_c_haines@btinternet.com \
--cc=selinux@tycho.nsa.gov \
--cc=slawrence@tresys.com \
/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.