From: Paul Moore <pmoore@redhat.com>
To: Joshua Brindle <brindle@quarksecurity.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: New SELinux userspace release supporting extended ioctl permissions?
Date: Fri, 06 Nov 2015 12:28 -0500 [thread overview]
Message-ID: <15905901.1XIAY3c11E@sifl> (raw)
In-Reply-To: <563CD60D.9090605@quarksecurity.com>
On Friday, November 06, 2015 11:32:13 AM Joshua Brindle wrote:
> Dominick Grift wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA512
> >
> > On Fri, Nov 06, 2015 at 10:37:35AM -0500, Paul Moore wrote:
> >> Now that Linux 4.3 has been released with the extended ioctl permissions,
> >> are we planning to make a new userspace release so that we can take
> >> advantage of this new functionality? I believe all the necessary
> >> patches have been merged, no?
> >
> > Are you referring to anything in particular?
> >
> > There is already some support:
> > https://github.com/SELinuxProject/selinux/commit/ef93dfe0393c4a60483c3f77
> > 29dd98a2f886606a
>
> I think he means actually making a release...
Yes, exactly. I'm old fashioned that way.
--
paul moore
security @ redhat
next prev parent reply other threads:[~2015-11-06 17:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 15:37 New SELinux userspace release supporting extended ioctl permissions? Paul Moore
2015-11-06 16:26 ` Dominick Grift
2015-11-06 16:32 ` Joshua Brindle
2015-11-06 17:21 ` Roberts, William C
2015-11-06 17:28 ` Paul Moore [this message]
2015-11-06 17:51 ` Jeffrey Vander Stoep
2015-11-06 18:11 ` Dominick Grift
2015-11-06 20:40 ` Jeffrey Vander Stoep
2015-11-06 21:02 ` Roberts, William C
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=15905901.1XIAY3c11E@sifl \
--to=pmoore@redhat.com \
--cc=brindle@quarksecurity.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.