Re: [PATCH V32 01/27] Add the ability to lock down access to the running kernel image

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

Subject: Re: [PATCH V32 01/27] Add the ability to lock down access to the running kernel image
From: Matthew Garrett <mjg59@xxxxxxxxxx>
Date: Mon, 29 Apr 2019 15:56:44 -0700
Cc: LSM List <linux-security-module@xxxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, David Howells <dhowells@xxxxxxxxxx>, Linux API <linux-api@xxxxxxxxxxxxxxx>, Andy Lutomirski <luto@xxxxxxxxxx>
In-reply-to: <20190404003249.14356-2-matthewgarrett@google.com>
References: <20190404003249.14356-1-matthewgarrett@google.com> <20190404003249.14356-2-matthewgarrett@google.com>

Hi James,

What's the best way forward with this? I'm still not entirely clear on
how it can be implemented purely as an LSM, but if you have ideas on
what sort of implementation you'd prefer I'm happy to work on that.

Follow-Ups:
- Re: [PATCH V32 01/27] Add the ability to lock down access to the running kernel image
  - From: James Morris

References:
- [PATCH V32 0/27] Lockdown patches for 5.2
  - From: Matthew Garrett
- [PATCH V32 01/27] Add the ability to lock down access to the running kernel image
  - From: Matthew Garrett

Prev by Date: Re: [RFC PATCH for 5.2 10/10] rseq/selftests: mips: use break instruction for RSEQ_SIG
Next by Date: Re: RFC: on adding new CLONE_* flags [WAS Re: [PATCH 0/4] clone: add CLONE_PIDFD]
Previous by thread: Re: [PATCH V32 01/27] Add the ability to lock down access to the running kernel image
Next by thread: Re: [PATCH V32 01/27] Add the ability to lock down access to the running kernel image
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