From: John Johansen <john.johansen@canonical.com>
To: James Morris <jmorris@namei.org>,
Casey Schaufler <casey@schaufler-ca.com>
Cc: LSM <linux-security-module@vger.kernel.org>,
Paul Moore <paul@paul-moore.com>,
Kees Cook <keescook@chromium.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
LKLM <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 0/3] LSM: security module information improvements
Date: Thu, 27 Oct 2016 15:57:21 -0700 [thread overview]
Message-ID: <5e40bbb4-1955-8432-e12a-690c924ccd5d@canonical.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1610280928280.15246@namei.org>
On 10/27/2016 03:32 PM, James Morris wrote:
> On Wed, 26 Oct 2016, Casey Schaufler wrote:
>
>> Create interfaces that make it possible to deal with process
>> attributes in the face of multiple "major" security modules.
>
> We don't have support for multiple major modules currently (perhaps ever),
> so I'm not merging infrastructure which is only useful for them.
>
>>
>> Patch 1/3 adds /sys/kernel/security/lsm, which provides
>> a list of the active security modules on the system.
>>
>> $ cat /sys/kernel/security/lsm
>> capability,yama,loadpin,smack
>
> This may make sense on its own. Has anyone requested this, or is likely
> to adopt it into a distro?
>
>
This is quite useful and Ubuntu will likely adopt it for the 17.04 release
next prev parent reply other threads:[~2016-10-27 23:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 23:56 Casey Schaufler
2016-10-27 0:01 ` [PATCH v6 1/3] LSM: Add /sys/kernel/security/lsm Casey Schaufler
2016-11-01 12:53 ` Tetsuo Handa
2016-11-01 17:25 ` Casey Schaufler
2016-11-04 14:11 ` Tetsuo Handa
2016-10-27 0:01 ` [PATCH v6 2/3] LSM: module hierarchy in /proc/.../attr Casey Schaufler
2016-10-27 0:01 ` [PATCH v6 3/3] LSM: Add context interface for proc attrs Casey Schaufler
2016-10-27 21:34 ` [PATCH v6 0/3] LSM: security module information improvements Kees Cook
2016-10-27 22:32 ` James Morris
2016-10-27 22:57 ` John Johansen [this message]
2016-10-28 0:05 ` Casey Schaufler
2016-10-28 9:28 ` James Morris
2016-10-28 15:22 ` Casey Schaufler
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=5e40bbb4-1955-8432-e12a-690c924ccd5d@canonical.com \
--to=john.johansen@canonical.com \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--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
all inboxes | Powered by JetHome®