From: Petr Lautrbach <plautrba@redhat.com>
To: "selinux\@vger.kernel.org" <selinux@vger.kernel.org>
Subject: ANN: SELinux userspace release 2019-03-15 / 2.9
Date: Fri, 15 Mar 2019 17:12:53 +0100 [thread overview]
Message-ID: <pjda7hw5d6i.fsf@redhat.com> (raw)
The 2019-03-15 / 2.9 release for the SELinux userspace is now
available at:
https://github.com/SELinuxProject/selinux/wiki/Releases
Thanks to all the contributors to this release!
User-visible changes:
* Spelling errors were fixed in libselinux man pages
* audit2allow supports xperms now. There are new '-x'/'--xperms'
options which
turn on generating of extended permisssion AV rules.
* semanage login is fixed in order not to log two audit events
which one of them
was correct.
* libsemanage resets umask before creating directories so that
file permissions
should not change after a change is committed.
* Correct user name is used in ROLE_REMOVE audit events
* The noise produced by checkpolicy command line tool is reduced
now.
* A new option '-S' or '--sort' is added to checkpolicy to sort
the ocontexts
before writing out the binary policy.
* sepolicy and semanage accept aliases now.
* Deprecated at_console statement was removed from dbus
configuration.
* semanage export output includes ibpkey and ibendport now.
* audit2why can be run as non-root user now.
* Added russian translations for man pages
* setfiles can once again be used on SELinux-disabled hosts to
label files,
* setfiles and restorecon once again correctly ignore files with
customizable
types,
* semanage login no longer fails if used with a group that has
many members,
* semanage boolean no longer fails if listing for a policy store
other than the
active one.
* By default, /usr/bin/python3 is used by Python scripts and for
building modules
with python bindings.
Packaging-relevant changes:
* Usage of DESTDIR in restorecond is consistent with other
directories now
* By default, /usr/bin/python3 is used by Python scripts and for
building modules
with python bindings. It's possible to switch to Python 2 using
the following commands:
$ pathfix.py -i/usr/bin/python `git grep -l -E
'^#!.*/usr/bin/python'`
$ make PYTHON=/usr/bin/python` to use Python 2 .
Issues fixed:
* https://github.com/SELinuxProject/selinux/issues/81
* https://github.com/SELinuxProject/selinux/issues/97
* https://github.com/SELinuxProject/selinux/issues/108
* https://github.com/SELinuxProject/selinux/issues/109
* https://github.com/SELinuxProject/selinux/issues/119
* https://github.com/SELinuxProject/selinux/issues/121
* https://github.com/SELinuxProject/selinux/issues/123
next reply other threads:[~2019-03-15 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 16:12 Petr Lautrbach [this message]
2019-03-17 12:09 ` ANN: SELinux userspace release 2019-03-15 / 2.9 Nicolas Iooss
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=pjda7hw5d6i.fsf@redhat.com \
--to=plautrba@redhat.com \
--cc=selinux@vger.kernel.org \
/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.