From: Dominick Grift <dac.override@gmail.com>
To: selinux@tycho.nsa.gov
Subject: Re: type inheritance in CIL
Date: Mon, 29 Jun 2015 09:56:52 +0200 [thread overview]
Message-ID: <20150629075651.GA8191@x250> (raw)
In-Reply-To: <5590F3DE.8070202@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
On Mon, Jun 29, 2015 at 09:29:34AM +0200, Miroslav Grepl wrote:
> Trying to make sandbox working using CIL but I see it does not support
> typeinherit statement.
One of those features that really define CIL but that is currently not available or fully working yet.
My suggestion is to study the "cilpolicy" (which is really just a snapshot of reference policy transformed to cil with hll i believe)
This will give you some pointers as to how to create an alternative implementation that achieves a similar result.
When you write CIL policy, there are some "bugs" to take into account and to workaround.
>
> --
> Miroslav Grepl
> Senior Software Engineer, SELinux Solutions
> Red Hat, Inc.
> _______________________________________________
> Selinux mailing list
> Selinux@tycho.nsa.gov
> To unsubscribe, send email to Selinux-leave@tycho.nsa.gov.
> To get help, send an email containing "help" to Selinux-request@tycho.nsa.gov.
--
02DFF788
4D30 903A 1CF3 B756 FB48 1514 3148 83A2 02DF F788
http://keys.gnupg.net/pks/lookup?op=vindex&search=0x314883A202DFF788
Dominick Grift
[-- Attachment #2: Type: application/pgp-signature, Size: 648 bytes --]
next prev parent reply other threads:[~2015-06-29 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 7:29 type inheritance in CIL Miroslav Grepl
2015-06-29 7:56 ` Dominick Grift [this message]
2015-06-29 11:19 ` Miroslav Grepl
2015-06-29 18:56 ` James Carter
2015-06-29 19:25 ` Dominick Grift
2015-06-29 20:22 ` James Carter
2015-06-30 8:37 ` Miroslav Grepl
2015-06-30 14:48 ` James Carter
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=20150629075651.GA8191@x250 \
--to=dac.override@gmail.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.