linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: Stephen Smalley <sds@tycho.nsa.gov>,
	Mimi Zohar <zohar@linux.vnet.ibm.com>,
	Paul Moore <paul@paul-moore.com>
Cc: James Morris <jmorris@namei.org>,
	James Morris <james.l.morris@oracle.com>,
	LSM <linux-security-module@vger.kernel.org>,
	LKLM <linux-kernel@vger.kernel.org>,
	Paul Moore <pmoore@redhat.com>,
	John Johansen <john.johansen@canonical.com>,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	Eric Paris <eparis@redhat.com>, Kees Cook <keescook@chromium.org>,
	Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [PATCH 0/7 v22] LSM: Multiple concurrent LSMs
Date: Thu, 07 May 2015 13:36:45 -0700	[thread overview]
Message-ID: <554BCCDD.9010901@schaufler-ca.com> (raw)
In-Reply-To: <554BC9A6.1020907@tycho.nsa.gov>

On 5/7/2015 1:23 PM, Stephen Smalley wrote:
> On 05/07/2015 04:22 PM, Mimi Zohar wrote:
>> On Thu, 2015-05-07 at 14:07 -0400, Paul Moore wrote:
>>> On Thu, May 7, 2015 at 10:47 AM, Casey Schaufler <casey@schaufler-ca.com> wrote:
>>>> On 5/7/2015 4:37 AM, James Morris wrote:
>>>>> On Sat, 2 May 2015, Casey Schaufler wrote:
>>>>>
>>>>>> Subject: [PATCH 0/7 v22] LSM: Multiple concurrent LSMs
>>>>> Please add all of the Acked-by etc. from the patch review process.
>>>> For v21 I had Acks from:
>>>>
>>>>         John Johansen <john.johansen@canonical.com>
>>>>         Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
>>>>         Stephen Smalley <sds@tycho.nsa.gov> (after patch 8/7)
>>>>         Kees Cook <keescook@chromium.org>
>>>>
>>>> Would you check out v22 and supply (or not) your Acks?
>>>>
>>>> Eric, Paul, it would be reassuring if you'd chime in as well.
>>> Kubernetes has swallowed Eric whole I'm afraid, I don't think you want
>>> to wait on him to review these patches.
>>>
>>> However, it is a bit ridiculous that I haven't had time to seriously
>>> review these patches yet; I promise to take a look and send my
>>> comments/ACKs before my head hits the pillow tonight.
>> Seems to be working with SELinux, EVM and IMA enabled.  I haven't tried
>> enabling an additional LSM.   Casey, do you have an additional LSM for
>> testing?
> I've tested SELinux+Yama.

The deepest "stack" you can have today is Capability+Yama+YourChoice.
You always get Capability, so you really only get to choose if you stack
Yama with something else. That's not more depth than you had before, but
the special case coding for Capability and Yama is replaced to the general
scheme.


  reply	other threads:[~2015-05-07 20:36 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-02 21:44 [PATCH 0/7 v22] LSM: Multiple concurrent LSMs Casey Schaufler
2015-05-02 22:10 ` [PATCH 1/7 v22] LSM: Split security.h Casey Schaufler
2015-05-07 20:41   ` Paul Moore
2015-05-02 22:10 ` [PATCH 2/7 v22] LSM: Add the comment to lsm_hooks.h Casey Schaufler
2015-05-07 20:42   ` Paul Moore
2015-05-02 22:11 ` [PATCH 3/7 v22] LSM: Remove a comment from security.h Casey Schaufler
2015-05-07 20:43   ` Paul Moore
2015-05-02 22:11 ` [PATCH 4/7 v22] LSM: Introduce security hook calling Macros Casey Schaufler
2015-05-07 21:02   ` Paul Moore
2015-05-02 22:11 ` [PATCH 5/7 v22] LSM: Add security module hook list heads Casey Schaufler
2015-05-07 21:03   ` Paul Moore
2015-05-02 22:11 ` [PATCH 6/7 v22] LSM: Switch to lists of hooks Casey Schaufler
2015-05-07 21:05   ` Paul Moore
2015-05-02 22:11 ` [PATCH 7/7 v22] LSM: Remove unused capability.c Casey Schaufler
2015-05-07 21:05   ` Paul Moore
2015-05-03 19:04 ` [PULL] LSM: Basic module stacking infrastructure for security-next Casey Schaufler
2015-05-07 11:37 ` [PATCH 0/7 v22] LSM: Multiple concurrent LSMs James Morris
2015-05-07 14:47   ` Casey Schaufler
2015-05-07 18:07     ` Paul Moore
2015-05-07 20:22       ` Mimi Zohar
2015-05-07 20:23         ` Stephen Smalley
2015-05-07 20:36           ` Casey Schaufler [this message]
2015-05-08 11:21             ` Mimi Zohar
2015-05-08 16:13               ` Casey Schaufler
2015-05-08 17:00                 ` Kees Cook
2015-05-08 17:54                   ` John Johansen
2015-05-09  1:41                     ` Tetsuo Handa
2015-05-07 17:04 ` Stephen Smalley
2015-05-09  2:07 ` [PULL] LSM: Basic module stacking infrastructure for security-next - Acked Casey Schaufler
2015-05-12  5:02   ` James Morris
2015-05-13  4:19     ` Casey Schaufler
2015-05-15 12:56       ` [PULL] LSM: Basic module stacking infrastructure for security-next- Acked Tetsuo Handa
2015-05-16 17:39         ` Casey Schaufler
2015-05-17  3:53           ` LSM: Basic module stacking infrastructure for security-next-Acked Tetsuo Handa
2015-05-19 17:45       ` [PULL] LSM: Basic module stacking infrastructure for security-next - Acked 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=554BCCDD.9010901@schaufler-ca.com \
    --to=casey@schaufler-ca.com \
    --cc=eparis@redhat.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=pmoore@redhat.com \
    --cc=sds@tycho.nsa.gov \
    --cc=zohar@linux.vnet.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).