From: Sven Vermeulen <sven.vermeulen@siphos.be>
To: Joshua Brindle <brindle@quarksecurity.com>
Cc: SELinux <SELinux@tycho.nsa.gov>
Subject: Re: [Ann] SELinux userspace release
Date: Thu, 25 Apr 2013 22:01:30 +0200 [thread overview]
Message-ID: <20130425200130.GA17297@siphos.be> (raw)
In-Reply-To: <CADjGSjhkWnxg6rEzUowJ4pU0icFYbboxeDh2ejZ6gpg83W0QYA@mail.gmail.com>
On Tue, Apr 23, 2013 at 10:34:52AM -0400, Joshua Brindle wrote:
> A new release of the SELinux userspace has been posted to:
> http://userspace.selinuxproject.org/trac/wiki/Releases
>
> Most of the changes were bug fixes related to leaking file descriptors and
> memory errors reported by Coverity. The full Changelog is in each package.
I had a few issues while getting this release in Gentoo.
https://bugs.gentoo.org/show_bug.cgi?id=467258
- libselinux does not provide selinux_current_policy_path() but this method is
used in policycoreutils in a number of locations.
I had to take the definition from this method from
http://svnweb.mageia.org/packages/cauldron/libselinux/current/SOURCES/libselinux-rhat.patch?revision=400400&view=co&pathrev=400400
(only included the definition in Gentoo for now). Seems that this is a
much-needed function (otherwise tools like semanage just break).
https://bugs.gentoo.org/show_bug.cgi?id=467264
- using semanage permissive fails with stacktrace referring to a Makefile on
a non-existing location (/usr/share/selinux/default/Makefile)
I have yet to find the culprit of this (getting late so that'll be for
tomorrow evening).
https://bugs.gentoo.org/show_bug.cgi?id=467268
- policycoreutils' sepolicy command requires yum python bindings
Since yum is not available on Gentoo, is this really necessary?
Wkr,
Sven Vermeulen
--
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:[~2013-04-25 20:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 14:34 [Ann] SELinux userspace release Joshua Brindle
2013-04-25 20:01 ` Sven Vermeulen [this message]
2013-04-25 23:15 ` Joshua Brindle
2013-04-26 6:36 ` Sven Vermeulen
2013-04-27 7:46 ` Sven Vermeulen
-- strict thread matches above, loose matches on Subject: below --
2014-05-06 17:57 [ANN] " Stephen Smalley
2014-05-10 12:03 ` Sven Vermeulen
2014-05-12 17:10 ` Daniel J Walsh
2013-10-30 18:08 Stephen Smalley
2013-10-30 18:33 ` Stephen Smalley
2012-09-24 23:52 Joshua Brindle
2012-02-17 3:37 [ANN} SELinux Userspace Release Joshua Brindle
2010-12-21 20:39 [ANN] SELinux Userspace release Chad Sellers
2010-05-25 21:11 Chad Sellers
2009-11-30 18:03 Chad Sellers
2009-07-31 14:18 Joshua Brindle
2009-04-03 18:05 [ANN] SELinux userspace release Joshua Brindle
2009-04-05 1:02 ` KaiGai Kohei
2009-04-06 17:09 ` Joshua Brindle
2009-04-07 13:13 ` KaiGai Kohei
2009-04-08 2:57 ` Eamon Walsh
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=20130425200130.GA17297@siphos.be \
--to=sven.vermeulen@siphos.be \
--cc=SELinux@tycho.nsa.gov \
--cc=brindle@quarksecurity.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.