From: Casey Schaufler <casey@schaufler-ca.com>
To: James Morris <jmorris@namei.org>
Cc: 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>,
Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@redhat.com>, Kees Cook <keescook@chromium.org>,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [PULL] LSM: Basic module stacking infrastructure for security-next - Acked
Date: Tue, 12 May 2015 21:19:57 -0700 [thread overview]
Message-ID: <5552D0ED.703@schaufler-ca.com> (raw)
In-Reply-To: <alpine.LRH.2.11.1505121501350.30679@namei.org>
On 5/11/2015 10:02 PM, James Morris wrote:
> On Fri, 8 May 2015, Casey Schaufler wrote:
>
>> James, here's an updated pull request for LSM stacking.
>> Acks have been applied.
>>
>> The following changes since commit b787f68c36d49bb1d9236f403813641efa74a031:
>>
>> Linux 4.1-rc1 (2015-04-26 17:59:10 -0700)
>>
>> are available in the git repository at:
>>
>> git@github.com:cschaufler/smack-next.git stacking-v22-acked
> fyi, this is not a public URN.
https://github.com/cschaufler/smack-next.git should work.
>
>> for you to fetch changes up to f17cd945a8761544ac9bfdaf55e952e558dbee3e:
> Applied to
> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next
>
Thank you. I'm glad I was able to address all of the feedback from the
earlier versions. Special thanks to Tetsuo, who really kept me honest,
and Kees, who kept encouraging me to try again.
LSM maintainers! You may want base you 4.2 trees off what James has now.
The changes in the security modules are significant enough that merging late
in the game could be inconvenient. If you want help, let me know, and I'll
do what I can to reduce the pain.
Anyone with an out-of-tree security module should start looking at what you
need to do sooner rather than later. Your best option is to get your
module mainlined, in which case I'm happy to help you help you update it.
next prev parent reply other threads:[~2015-05-13 4:20 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
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 [this message]
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=5552D0ED.703@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=penguin-kernel@i-love.sakura.ne.jp \
--cc=pmoore@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).