From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] ANN: Reference Policy contrib repository
Date: Wed, 14 Sep 2011 08:19:00 -0400 [thread overview]
Message-ID: <4E709BB4.8060800@tresys.com> (raw)
In-Reply-To: <4E6FCBC4.6030403@gmail.com>
On 09/13/11 17:31, Dominick Grift wrote:
> Op 9-9-2011 17:35, Christopher J. PeBenito schreef:
>> The core modules are critical modules on the system. This includes all of the kernel layer, most of the system and roles layers, some admin modules, such as bootloader, su, and sudo, and userspace object managers. It is possible to build a policy using only the core modules. It is important to ensure these modules are well reviewed to ensure quality, so Reference Policy can be used as a base for both general-purpose systems (e.g. Linux distributions) and custom systems. All remaining modules were moved to the contrib repository. An important thing to note is that in the future, modules may move between core and contrib as necessary.
>
> I like this, although i would prefer the core to be only the base
> modules (kernel layer) but it will not build without atleast a user,
> which is a pity.
This split was chosen because very few systems, if any, build their policy starting with only the kernel layer.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2011-09-14 12:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 15:35 ANN: Reference Policy contrib repository Christopher J. PeBenito
2011-09-09 15:35 ` [refpolicy] " Christopher J. PeBenito
2011-09-09 15:58 ` Robert Lee
2011-09-09 16:17 ` Christopher J. PeBenito
2011-09-09 16:17 ` [refpolicy] " Christopher J. PeBenito
2011-09-09 16:22 ` Guido Trentalancia
2011-09-09 16:28 ` Christopher J. PeBenito
2011-09-12 20:45 ` Daniel J Walsh
2011-09-13 21:12 ` Dominick Grift
2011-09-13 21:31 ` Dominick Grift
2011-09-14 12:19 ` Christopher J. PeBenito [this message]
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=4E709BB4.8060800@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.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.