Re: [PULL] LSM: Basic module stacking infrastructure for security-next - Acked

From: Kees Cook
Date: Tue May 19 2015 - 13:45:50 EST


On Tue, May 12, 2015 at 9:19 PM, Casey Schaufler <casey@xxxxxxxxxxxxxxxx> wrote:
> 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@xxxxxxxxxx: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.
>

(Sorry, been high latency for a bit...)

This is so great! Thanks for keeping it going. I will be reworking my
two out-of-tree LSMs and getting them resubmitted now that they can
sensibly stack. :)

Yay!

-Kees


--
Kees Cook
Chrome OS Security
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/