[V35,00/29] Kernel lockdown functionality

Message ID	20190715195946.223443-1-matthewgarrett@google.com (mailing list archive)
Headers	show Return-Path: <linux-security-module-owner@kernel.org> Date: Mon, 15 Jul 2019 12:59:17 -0700 Message-Id: <20190715195946.223443-1-matthewgarrett@google.com> Mime-Version: 1.0 Subject: [PATCH V35 00/29] Kernel lockdown functionality From: Matthew Garrett <matthewgarrett@google.com> To: jmorris@namei.org Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-security-module@vger.kernel.org Precedence: bulk
Series	Kernel lockdown functionality \| expand [V35,00/29] Kernel lockdown functionality [V35,01/29] security: Support early LSMs [V35,02/29] security: Add a "locked down" LSM hook [V35,03/29] security: Add a static lockdown policy LSM [V35,04/29] Enforce module signatures if the kernel is locked down [V35,05/29] Restrict /dev/{mem,kmem,port} when the kernel is locked down [V35,06/29] kexec_load: Disable at runtime if the kernel is locked down [V35,07/29] Copy secure_boot flag in boot params across kexec reboot [V35,08/29] kexec_file: split KEXEC_VERIFY_SIG into KEXEC_SIG and KEXEC_SIG_FORCE [V35,09/29] kexec_file: Restrict at runtime if the kernel is locked down [V35,10/29] hibernate: Disable when the kernel is locked down [V35,11/29] PCI: Lock down BAR access when the kernel is locked down [V35,12/29] x86: Lock down IO port access when the kernel is locked down [V35,13/29] x86/msr: Restrict MSR access when the kernel is locked down [V35,14/29] ACPI: Limit access to custom_method when the kernel is locked down [V35,15/29] acpi: Ignore acpi_rsdp kernel param when the kernel has been locked down [V35,16/29] acpi: Disable ACPI table override if the kernel is locked down [V35,17/29] Prohibit PCMCIA CIS storage when the kernel is locked down [V35,18/29] Lock down TIOCSSERIAL [V35,19/29] Lock down module params that specify hardware parameters (eg. ioport) [V35,20/29] x86/mmiotrace: Lock down the testmmiotrace module [V35,21/29] Lock down /proc/kcore [V35,22/29] Lock down tracing and perf kprobes when in confidentiality mode [V35,23/29] bpf: Restrict bpf when kernel lockdown is in confidentiality mode [V35,24/29] Lock down perf when in confidentiality mode [V35,25/29] kexec: Allow kexec_file() with appropriate IMA policy when locked down [V35,26/29] debugfs: Restrict debugfs when the kernel is locked down [V35,27/29] tracefs: Restrict tracefs when the kernel is locked down [V35,28/29] efi: Restrict efivar_ssdt_load when the kernel is locked down [V35,29/29] lockdown: Print current->comm in restriction messages

Message ID

20190715195946.223443-1-matthewgarrett@google.com (mailing list archive)

Headers

Date: Mon, 15 Jul 2019 12:59:17 -0700
Message-Id: <20190715195946.223443-1-matthewgarrett@google.com>
Mime-Version: 1.0
Subject: [PATCH V35 00/29] Kernel lockdown functionality
From: Matthew Garrett <matthewgarrett@google.com>
To: jmorris@namei.org
Cc: linux-security-module@vger.kernel.org,
        linux-kernel@vger.kernel.org, linux-api@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Sender: owner-linux-security-module@vger.kernel.org
Precedence: bulk

Series

Kernel lockdown functionality | expand

Minor updates to the previous patchset to take some review comments into account - no significant changes in functionality, other than that the eBPF patch now only disables the kernel read functions as requested.