[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170621114812.6aa3f62e@vega.skynet.aixah.de>
Date: Wed, 21 Jun 2017 11:48:12 +0200
From: Luis Ressel <aranea@...ah.de>
To: Paul Moore <paul@...l-moore.com>
Cc: Stephen Smalley <sds@...ho.nsa.gov>,
James Morris <james.l.morris@...cle.com>,
linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org, selinux@...ho.nsa.gov
Subject: Re: [PATCH] selinux: Assign proper class to PF_UNIX/SOCK_RAW
sockets
On Tue, 20 Jun 2017 17:43:38 -0400
Paul Moore <paul@...l-moore.com> wrote:
> Considering where we are at with respect to the merge window, let's
> shelve this for now and I'll merge it after the next merge window
> closes. In all likelihood I'll be sending selinux/next up to James
> later this week and I'd like this to sit in linux-next for longer than
> a few days.
That means the change will land in 4.14 at the earliest, right? (Just
out of curiosity.)
By the way, refpolicy only grants "socket" permissions to a handful of
domains, all of which also have the corresponding "unix_dgram_socket"
permissions. The fedora policy does the same (according to Stephen);
this only leaves custom policies to be potentially affected by this
change.
Given that the SOCK_RAW->SOCK_DGRAM translation is obscure enough not to
be documented anywhere outside the kernel sources, I doubt there are
many users of it, anyway.
Regards,
Luis Ressel
Powered by blists - more mailing lists