All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Lawrence <slawrence@tresys.com>
To: Richard Haines <richard_c_haines@btinternet.com>
Cc: James Carter <jwcart2@tycho.nsa.gov>,
	Dominick Grift <dominick.grift@gmail.com>,
	SELinux List <selinux@tycho.nsa.gov>
Subject: Re: Update to CIL
Date: Mon, 21 Oct 2013 09:36:33 -0400	[thread overview]
Message-ID: <52652DE1.4020504@tresys.com> (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:
>

Thanks for the bug reports and examples. Very helpful.

> 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.
>
> 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".
>
> 3) Fails to resolve neverallow "*". The "neverallow-STAR.cil" module demos
>     this error.
>
> 4) Not sure if this is a bug or 'as designed', I tried using "in" in a
>     booleanif statement but failed. The "in-boolean.cil" module demos
>     this error.
>

This should not be allowed. The only thing that should be allowed in a 
booleanif statement are typetransitions, typerules, and avrules.


> These only apply to the Tresys compiler (as do 2, 3, & 4):
> 5) Does not expand all entries in a typeattribute for allow rules within
>     a boolean. The "ta-bool-error.cil" module demos this error.
>
> 6) Neverallow fails when rule defined in a dontaudit rule. The NSA compiler
>     and checkpolicy do not generate an error.  The "neverallow-error.cil"
>     module demos this error.
>

I would start only using Jim's repo. The changes to that repo have fixed 
many of the problems. It is what we are working on.

> The attached "cil-base.cil" supplies the user, role etc. requirements
>
> Finally I know the NSA version resolves constraints okay now, but the output
> is reversed in Tresys. The "mlsconstrain-diff.cil" shows the difference but
> in the end they resolve to the same. I have not tried complex constraints.
>
> Hope all this helps

Very helpful. Thanks!

> Richard
>


--
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.

  reply	other threads:[~2013-10-21 13:36 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 [this message]
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   ` Update to CIL James Carter
2013-10-23 13:59 ` 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=52652DE1.4020504@tresys.com \
    --to=slawrence@tresys.com \
    --cc=dominick.grift@gmail.com \
    --cc=jwcart2@tycho.nsa.gov \
    --cc=richard_c_haines@btinternet.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.