From: "David A. Wheeler" <dwheeler@dwheeler.com>
To: "Casey Schaufler" <casey@schaufler-ca.com>
Cc: "LSM" <linux-security-module@vger.kernel.org>,
"James Morris" <jmorris@namei.org>,
"John Johansen" <john.johansen@canonical.com>,
"Stephen Smalley" <sds@tycho.nsa.gov>,
"Paul Moore" <paul@paul-moore.com>,
"Tetsuo Handa" <penguin-kernel@i-love.sakura.ne.jp>,
"Kees Cook" <keescook@chromium.org>,
"LKLM" <linux-kernel@vger.kernel.org>,
"James Morris" <james.l.morris@oracle.com>
Subject: Re: [PATCH v3 1/3] LSM: Add /sys/kernel/security/lsm
Date: Tue, 14 Jun 2016 18:25:50 -0400 (EDT) [thread overview]
Message-ID: <E1bCwmM-0004l1-PF@rmm6prod02.runbox.com> (raw)
In-Reply-To: <d2d4b12c-aec7-59b2-ade0-1344b442003a@schaufler-ca.com>
On Fri, 10 Jun 2016 14:25:45 -0700, Casey Schaufler <casey@schaufler-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
next prev parent reply other threads:[~2016-06-14 22:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 21:21 [PATCH v3 0/3] LSM: module hierarchy in /proc/.../attr Casey Schaufler
2016-06-10 21:25 ` [PATCH v3 1/3] LSM: Add /sys/kernel/security/lsm Casey Schaufler
2016-06-14 18:41 ` Kees Cook
2016-06-14 19:32 ` Casey Schaufler
2016-06-14 22:25 ` David A. Wheeler [this message]
2016-06-10 21:25 ` [PATCH v3 2/3] LSM: module hierarchy in /proc/.../attr Casey Schaufler
2016-06-14 18:43 ` Kees Cook
2016-06-14 19:27 ` Casey Schaufler
2016-06-14 21:24 ` Kees Cook
2016-06-10 21:25 ` [PATCH v3 3/3] LSM: Add context interface for proc attr Casey Schaufler
2016-06-14 18:57 ` Kees Cook
2016-06-14 20:19 ` Casey Schaufler
2016-06-14 21:07 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1bCwmM-0004l1-PF@rmm6prod02.runbox.com \
--to=dwheeler@dwheeler.com \
--cc=casey@schaufler-ca.com \
--cc=james.l.morris@oracle.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=sds@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox