[PATCH security-next v3 00/29] LSM: Explict LSM ordering
Kees Cook
keescook at chromium.org
Fri Sep 28 20:54:33 UTC 2018
On Fri, Sep 28, 2018 at 1:33 PM, Stephen Smalley <sds at tycho.nsa.gov> wrote:
> On 09/28/2018 04:25 PM, Stephen Smalley wrote:
>>
>> On 09/28/2018 04:01 PM, Kees Cook wrote:
>>>
>>> On Fri, Sep 28, 2018 at 8:55 AM, Casey Schaufler <casey at schaufler-ca.com>
>>> wrote:
>>>>
>>>> On 9/24/2018 5:18 PM, Kees Cook wrote:
>>>>>
>>>>> v3:
>>>>> - add CONFIG_LSM_ENABLE and refactor resulting logic
>>>>
>>>>
>>>> Kees, you can add my
>>>>
>>>> Reviewed-by:Casey Schaufler <casey at schaufler-ca.com>
>>>>
>>>> for this entire patch set. Thank you for taking this on, it's
>>>> a significant and important chunk of the LSM infrastructure
>>>> update.
>>>
>>>
>>> Thanks!
>>>
>>> John, you'd looked at this a bit too -- do the results line up with
>>> your expectations?
>>>
>>> Any thoughts from SELinux, TOMOYO, or IMA folks?
>>
>>
>> What's it relative to? First patch fails for me on current security/next.
>
> Never mind - user error ;)
FWIW, it's against v4.19-rc2.
>> Is there a branch in your repo that has the v3 patches?
>
> But still wondered about this one.
Oops! Sorry, I didn't push to kernel.org. Now pushed!
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=lsm/ordering-v3
(and "preview" v4 also with Reviewed-bys added and a cosmetic fix.)
-Kees
--
Kees Cook
Pixel Security
More information about the Linux-security-module-archive
mailing list