From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: lkcl luke <luke.leighton@gmail.com>
Cc: <selinux@tycho.nsa.gov>
Subject: Re: B2G
Date: Fri, 16 Mar 2012 10:21:31 -0400 [thread overview]
Message-ID: <4F634C6B.2090804@tresys.com> (raw)
In-Reply-To: <CAPweEDzK22daM9ue26tMZ_6HbrFwEZxTfVUXhea31GFO4x0=Qw@mail.gmail.com>
On 03/16/12 01:46, lkcl luke wrote:
> second: did that idea of dynamically allowing bits of binary-compiled
> se-linux permissions ever get implemented? last time i was on this
> list (eek, 2004?), the whole SE/Linux precompiled blob was just that:
> one huge humungous gelatinous blob that you couldn't mess with, not
> without doing a tooootal recompile using the m4 macros.
Yes, we do have modular policy now. Right now they are compiled, but hopefully we'll eventually be able to set to text modules. You compile .pp files that have some compiled policy and optional a .fc, and link them together into the policy.2x
> third: are them happy m4 macros still about? :) did anyone invent
> anything more... oo.. user-friendly shall we say? i quite liked them
> once i got used to it but i'm a bit concerned about the m4 macro
> language's obtuseness, if people in the B2G group were to be expected
> to cope with them. or, more to the point, if application developers
> were expected to be able to cope.
Yes. In a very different form than the NSA example policy: http://oss.tresys.com/projects/refpolicy
Hopefully CIL will be completed, as that will make it possible to make Reference Policy a proper language and most if not all of the M4 will be dropped. http://userspace.selinuxproject.org/trac/wiki/CilDesign
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
--
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:[~2012-03-16 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 5:46 B2G lkcl luke
2012-03-16 7:39 ` B2G Patrick K., ITF
2012-03-16 13:29 ` B2G lkcl luke
2012-03-16 13:22 ` B2G Stephen Smalley
2012-03-16 13:45 ` B2G lkcl luke
2012-03-16 14:33 ` B2G Radzykewycz, T (Radzy)
2012-03-16 14:21 ` Christopher J. PeBenito [this message]
2012-03-16 14:30 ` B2G lkcl luke
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=4F634C6B.2090804@tresys.com \
--to=cpebenito@tresys.com \
--cc=luke.leighton@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.