Re: [PATCH V31 25/25] debugfs: Disable open() when kernel is locked down

From: Matthew Garrett
Date: Tue Mar 26 2019 - 15:22:10 EST

Next message: Andy Lutomirski: "Re: [PATCH 23/27] bpf: Restrict kernel image access functions when the kernel is locked down"
Previous message: Andy Lutomirski: "Re: [PATCH V31 22/25] bpf: Restrict bpf when kernel lockdown is in confidentiality mode"
In reply to: Andy Lutomirski: "Re: [PATCH V31 25/25] debugfs: Disable open() when kernel is locked down"
Next in thread: Greg KH: "Re: [PATCH V31 25/25] debugfs: Disable open() when kernel is locked down"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, Mar 26, 2019 at 12:20 PM Andy Lutomirski <luto@xxxxxxxxxx> wrote:
> Ugh. Some of those files are very useful. Could this perhaps still
> allow O_RDONLY if we're in INTEGRITY mode?

The previous implementation did, but Greg wanted it to go away entirely.

Next message: Andy Lutomirski: "Re: [PATCH 23/27] bpf: Restrict kernel image access functions when the kernel is locked down"
Previous message: Andy Lutomirski: "Re: [PATCH V31 22/25] bpf: Restrict bpf when kernel lockdown is in confidentiality mode"
In reply to: Andy Lutomirski: "Re: [PATCH V31 25/25] debugfs: Disable open() when kernel is locked down"
Next in thread: Greg KH: "Re: [PATCH V31 25/25] debugfs: Disable open() when kernel is locked down"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]