From: Matt Brown <matt@nmatt.com>
To: Casey Schaufler <casey@schaufler-ca.com>,
LSM <linux-security-module@vger.kernel.org>,
James Morris <jmorris@namei.org>
Cc: John Johansen <john.johansen@canonical.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Paul Moore <paul@paul-moore.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
Kees Cook <keescook@chromium.org>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
LKLM <linux-kernel@vger.kernel.org>
Subject: Re: [kernel-hardening] [PATCH 0/6] LSM: Security module blob management
Date: Thu, 8 Jun 2017 16:58:01 -0400 [thread overview]
Message-ID: <2a28d30a-22d3-33ff-581c-f1347fbbae74@nmatt.com> (raw)
In-Reply-To: <59cec608-608e-6de6-21d9-bdec7b0ded3b@schaufler-ca.com>
On 6/8/17 4:43 PM, Casey Schaufler wrote:
> Subject: [PATCH 0/6] LSM: Security module blob management
>
> This patch set moves management of security blobs out of
> the Linux security modules and into the security module
> infrastructure. This allows "major" security modules that
> use blobs to be stacked, just as "minor" modules that
> do not use blobs can be stacked today. It stops short of
> providing a safe interface for the Netlabel and SO_PEERSEC.
> As a result, any of the existing security modules may be
> used in combination except for SELinux and Smack.
Very excited about this! I can definitely see use cases for special
purpose LSMs that require data blobs but do not replace things like
SELinux, SMACK or AppArmor. I have had a few ideas recently that would
not be possible under the current setup of one shared blob.
Matt
next prev parent reply other threads:[~2017-06-08 20:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 20:43 Casey Schaufler
2017-06-08 20:49 ` [PATCH 1/6] procfs-add-smack-subdir-to-attrs Casey Schaufler
2017-06-08 20:49 ` [PATCH 2/6] LSM-manage-credential-security-blobs Casey Schaufler
2017-06-08 20:49 ` [PATCH 3/6] LSM: Manage file security blobs Casey Schaufler
2017-06-08 20:49 ` [PATCH 4/6] LSM: manage task " Casey Schaufler
2017-06-08 20:50 ` [PATCH 5/6] LSM: Infrastructure management of the remaining blobs Casey Schaufler
2017-06-08 20:50 ` [PATCH 6/6] LSM: general but not extreme module stacking Casey Schaufler
2017-06-08 20:58 ` Matt Brown [this message]
2017-06-09 3:54 ` [kernel-hardening] [PATCH 0/6] LSM: Security module blob management James Morris
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=2a28d30a-22d3-33ff-581c-f1347fbbae74@nmatt.com \
--to=matt@nmatt.com \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--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®