[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5j+n8SviN12d3JkCKPA4rL9awbT2U2QyeiB40TykpELRgQ@mail.gmail.com>
Date: Wed, 18 Jan 2017 13:01:27 -0800
From: Kees Cook <keescook@...omium.org>
To: Paul Moore <paul@...l-moore.com>
Cc: James Morris <jmorris@...ei.org>,
Casey Schaufler <casey@...aufler-ca.com>,
LSM <linux-security-module@...r.kernel.org>,
John Johansen <john.johansen@...onical.com>,
Stephen Smalley <sds@...ho.nsa.gov>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
LKLM <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] LSM: Add /sys/kernel/security/lsm
On Wed, Jan 18, 2017 at 11:22 AM, Paul Moore <paul@...l-moore.com> wrote:
> On Wed, Jan 18, 2017 at 7:43 AM, James Morris <jmorris@...ei.org> wrote:
>> On Tue, 17 Jan 2017, Casey Schaufler wrote:
>>
>>> Subject: [PATCH] LSM: Add /sys/kernel/security/lsm
>>>
>>> I am still tired of having to find indirect ways to determine
>>> what security modules are active on a system. I have added
>>> /sys/kernel/security/lsm, which contains a comma separated
>>> list of the active secuirty modules. No more groping around
>>> in /proc/filesystems or other clever hacks.
>>>
>>> Unchanged from previous versions except for being updated
>>> to the latest security next branch.
>>>
>>
>> Any objections to merging this?
>>
>
> I'm fairly certain I ack'd a prior version of this at one point ...
>
> Acked-by: Paul Moore <paul@...l-moore.com>
Yeah, me too.
Acked-by: Kees Cook <keescook@...omium.org>
-Kees
--
Kees Cook
Nexus Security
Powered by blists - more mailing lists