[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <E1bCwmM-0004l1-PF@rmm6prod02.runbox.com>
Date: Tue, 14 Jun 2016 18:25:50 -0400 (EDT)
From: "David A. Wheeler" <dwheeler@...eeler.com>
To: "Casey Schaufler" <casey@...aufler-ca.com>
CC: "LSM" <linux-security-module@...r.kernel.org>,
"James Morris" <jmorris@...ei.org>,
"John Johansen" <john.johansen@...onical.com>,
"Stephen Smalley" <sds@...ho.nsa.gov>,
"Paul Moore" <paul@...l-moore.com>,
"Tetsuo Handa" <penguin-kernel@...ove.sakura.ne.jp>,
"Kees Cook" <keescook@...omium.org>,
"LKLM" <linux-kernel@...r.kernel.org>,
"James Morris" <james.l.morris@...cle.com>
Subject: Re: [PATCH v3 1/3] LSM: Add /sys/kernel/security/lsm
On Fri, 10 Jun 2016 14:25:45 -0700, Casey Schaufler <casey@...aufler-ca.com> wrote:
> Subject: [PATCH v3 1/3] LSM: Add /sys/kernel/security/lsm
> I got 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 security modules. No
> more groping around in /proc/filesystems, which won't
> help if the module doesn't support its own filesystem.
Great idea, thanks for doing it.
--- David A. Wheeler
Powered by blists - more mailing lists