[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jJDeFUKeSSxDEf4-HG4zfJFgU3ahs83TQtV1iPTrKY40Q@mail.gmail.com>
Date: Mon, 13 Feb 2017 09:29:08 -0800
From: Kees Cook <keescook@...omium.org>
To: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
Cc: James Morris <jmorris@...ei.org>,
linux-security-module <linux-security-module@...r.kernel.org>,
"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>
Subject: Re: Re: [RFC PATCH 2/4] security: mark nf ops in
SELinux and Smack as __ro_after_init
On Mon, Feb 13, 2017 at 3:29 AM, Tetsuo Handa
<penguin-kernel@...ove.sakura.ne.jp> wrote:
> James Morris wrote:
>> Both SELinux and Smack register Netfilter operations during init,
>> which then don't change. Mark these ops as __ro_after_init.
>>
>> Signed-off-by: James Morris <james.l.morris@...cle.com>
>
> This patch breaks CONFIG_SECURITY_SELINUX_DISABLE=y + SELINUX=disabled in /etc/selinux/config case,
> doesn't it? Although I heard that SELinux is planning to remove CONFIG_SECURITY_SELINUX_DISABLE,
> CONFIG_SECURITY_SELINUX_DISABLE is valid as of current linux-security.git#next .
We could fold that removal into this series?
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
