[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.20.1701190959450.23247@namei.org>
Date: Thu, 19 Jan 2017 10:00:12 +1100 (AEDT)
From: James Morris <jmorris@...ei.org>
To: Kees Cook <keescook@...omium.org>
cc: Paul Moore <paul@...l-moore.com>,
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, 18 Jan 2017, Kees Cook wrote:
> 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>
>
Casey: next time, please remember to include previous acks.
--
James Morris
<jmorris@...ei.org>
Powered by blists - more mailing lists