Re: [PATCH V33 02/30] security: Add a "locked down" LSM hook

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH V33 02/30] security: Add a "locked down" LSM hook
From: Matthew Garrett <mjg59@xxxxxxxxxx>
Date: Fri, 21 Jun 2019 12:29:15 -0700
Cc: James Morris <jmorris@xxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Linux API <linux-api@xxxxxxxxxxxxxxx>
In-reply-to: <201906202022.B09ED6E0@keescook>
References: <20190621011941.186255-1-matthewgarrett@google.com> <20190621011941.186255-3-matthewgarrett@google.com> <201906202022.B09ED6E0@keescook>

On Thu, Jun 20, 2019 at 8:23 PM Kees Cook <keescook@xxxxxxxxxxxx> wrote:

> bikeshed: can this just be called "security_locked_down" without the
> "is"?

Sure.

References:
- [PATCH V33 00/30] Lockdown as an LSM
  - From: Matthew Garrett
- [PATCH V33 02/30] security: Add a "locked down" LSM hook
  - From: Matthew Garrett
- Re: [PATCH V33 02/30] security: Add a "locked down" LSM hook
  - From: Kees Cook

Prev by Date: Re: [PATCH V33 01/30] security: Support early LSMs
Next by Date: Re: [PATCH V33 03/30] security: Add a static lockdown policy LSM
Previous by thread: Re: [PATCH V33 02/30] security: Add a "locked down" LSM hook
Index(es):
- Date
- Thread

[Index of Archives] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]

Powered by Linux