From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: SELinux Mail List <selinux@tycho.nsa.gov>
Subject: ANN: Reference Policy Release
Date: Tue, 02 Aug 2005 11:49:51 -0400 [thread overview]
Message-ID: <1122997791.26992.27.camel@sgc> (raw)
A new release of the SELinux Reference Policy is now available on
Sourceforge from http://serefpolicy.sourceforge.net. The change log
follows at the bottom of the email. In particular, the policy now works
as a targeted policy so that people can begin testing it on
non-production machines. There is a guide to switching a Fedora Core 4
system over to a targeted Reference Policy on Sourceforge
(http://serefpolicy.sourceforge.net/index.php?page=switch).
Again, for those that are interesting in contributing, right now the
best help would be to convert existing policies over to reference
policy; there is a list of modules on the status page on Sourceforge.
We are using the NSA example policy 1.23.2 as a baseline for the
policies (also available on the download page), and we ask that these
policies are used when converting modules. After all of the policies
are converted over, then we will update reference policy to the current
NSA CVS policy.
20050802 (2 Aug 2005)
* Fix comparison bug in fc_sort.
* Fix handling of ordered and unordered HTML lists.
* Corenetwork now supports multiple network interfaces having the
same type.
* Doc tool now creates pages for global Booleans and global tunables.
* Doc tool now links directly to the interface/template in the
module page when it is selected in the interface/template index.
* Added support for layer summaries.
* Added policies:
ipsec
nscd
pcmcia
raid
--
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150
--
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 reply other threads:[~2005-08-02 15:55 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 15:49 Christopher J. PeBenito [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-26 15:57 ANN: Reference Policy Release Christopher J. PeBenito
2005-09-07 17:22 Christopher J. PeBenito
2005-09-22 20:56 Christopher J. PeBenito
2005-10-19 21:50 Christopher J. PeBenito
2005-12-07 16:40 Christopher J. PeBenito
2005-12-15 22:28 ` Serge E. Hallyn
2005-12-16 17:59 ` Daniel J Walsh
2005-12-18 23:20 ` Serge E. Hallyn
2006-01-03 15:48 ` Christopher J. PeBenito
2006-01-17 21:31 Christopher J. PeBenito
2006-03-07 15:28 Christopher J. PeBenito
2006-10-19 12:57 Christopher J. PeBenito
2006-12-12 22:35 Christopher J. PeBenito
2007-04-17 15:07 Christopher J. PeBenito
2007-04-19 20:45 ` Manoj Srivastava
2007-04-19 20:56 ` Karl MacMillan
2007-04-19 23:10 ` Manoj Srivastava
2007-06-29 17:30 Christopher J. PeBenito
2007-09-28 15:19 Christopher J. PeBenito
2007-10-02 15:29 ` Shintaro Fujiwara
2007-12-14 18:56 Christopher J. PeBenito
2008-04-02 18:14 Christopher J. PeBenito
2008-07-02 15:37 Christopher J. PeBenito
2008-10-14 18:34 Christopher J. PeBenito
2008-12-10 20:24 Christopher J. PeBenito
2009-07-30 18:45 Christopher J. PeBenito
2009-11-17 15:28 Christopher J. PeBenito
2010-05-25 20:02 Christopher J. PeBenito
2010-12-14 16:39 Christopher J. PeBenito
2011-07-26 18:44 Christopher J. PeBenito
2012-02-15 20:19 Christopher J. PeBenito
2012-07-26 16:41 Christopher J. PeBenito
2013-04-24 20:56 Christopher J. PeBenito
2014-03-11 13:33 Christopher J. PeBenito
2014-12-03 19:31 Christopher J. PeBenito
2015-12-08 15:49 Christopher J. PeBenito
2016-10-23 21:29 Chris PeBenito
2016-11-02 4:13 ` Russell Coker
2016-11-02 22:19 ` Chris PeBenito
2017-02-04 19:02 Chris PeBenito
2018-07-01 17:40 ANN: Reference Policy release Chris PeBenito
2019-02-01 20:22 Chris PeBenito
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=1122997791.26992.27.camel@sgc \
--to=cpebenito@tresys.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.