From: Steve Lawrence <slawrence@tresys.com>
To: SELinux List <selinux@tycho.nsa.gov>
Subject: SELinux Userspace Release: 20140826-rc6
Date: Wed, 12 Nov 2014 08:50:05 -0500 [thread overview]
Message-ID: <5463658D.7050702@tresys.com> (raw)
The sixth release candidate for the next release of SELinux Userspace
[1] is now available. The tarballs have been built and can be downloaded
from the Releases wiki page [2]. Changes since rc5 include:
- updates to pp2cil compiler to mimic 'requires' in CIL, fixing a bug
that prevented a small set of optional blocks from being correctly
disabled [4]
- updates to pp2cil compiler to correctly scope type aliases, fixing a
bug that causes errors if a type alias referenced a type in a disabled
optional block [5]
As with the previous rc, action after installing the release candidate
is required to migrate the policy store from /etc/selinux to
/var/lib/selinux if it has not already been migrated. Detailed
information about this process can be found on the Policy Store
Migration wiki page [3].
Also, because the pp2cil compiler has been updated, any cached CIL
modules must be rebuilt. This can be done with the --ignore-module-cache
semodule option.
Please give this a test and let us know if you find any problems.
Thanks,
- Steve
[1] https://github.com/SELinuxProject/selinux
[2] https://github.com/SELinuxProject/selinux/wiki/Releases
[3] https://github.com/SELinuxProject/selinux/wiki/Policy-Store-Migration
[4] http://marc.info/?l=selinux&m=141537621807753&w=2
[5] http://marc.info/?l=selinux&m=141537664108369&w=2
next reply other threads:[~2014-11-12 13:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 13:50 Steve Lawrence [this message]
2014-11-14 21:09 ` SELinux Userspace Release: 20140826-rc6 Sven Vermeulen
2014-11-24 10:15 ` Sven Vermeulen
2014-11-24 11:26 ` Dominick Grift
2014-11-24 15:15 ` Sven Vermeulen
2014-11-27 12:23 ` Sven Vermeulen
2014-11-27 17:38 ` Dominick Grift
2014-11-27 20:14 ` Sven Vermeulen
2014-12-02 15:03 ` Steve Lawrence
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=5463658D.7050702@tresys.com \
--to=slawrence@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.