[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1750975839-32463-1-git-send-email-hamzamahfooz@linux.microsoft.com>
Date: Thu, 26 Jun 2025 15:10:37 -0700
From: Hamza Mahfooz <hamzamahfooz@...ux.microsoft.com>
To: linux-kernel@...r.kernel.org
Cc: Ard Biesheuvel <ardb@...nel.org>,
Paul Moore <paul@...l-moore.com>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Yue Haibing <yuehaibing@...wei.com>,
Tanya Agarwal <tanyaagarwal25699@...il.com>,
Kees Cook <kees@...nel.org>,
linux-efi@...r.kernel.org,
linux-security-module@...r.kernel.org,
Hamza Mahfooz <hamzamahfooz@...ux.microsoft.com>
Subject: [PATCH 0/2] Secure Boot lock down
All major distros have had carried a version of this patch-set
out of tree for sometime now, but with a bunch of magic (typically
sprinkled in setup_arch()). Though we can avoid those architecture
specific quirks if we call efi_get_secureboot_mode() from
efisubsys_init() and that allows us to have a generic solution.
Hamza Mahfooz (2):
security: introduce security_lock_kernel_down()
efi: introduce EFI_KERNEL_LOCK_DOWN_IN_SECURE_BOOT
drivers/firmware/efi/Kconfig | 10 ++++++++++
drivers/firmware/efi/efi.c | 9 +++++++++
include/linux/lsm_hook_defs.h | 1 +
include/linux/security.h | 8 ++++++++
security/lockdown/lockdown.c | 1 +
security/security.c | 15 +++++++++++++++
6 files changed, 44 insertions(+)
--
2.49.0
Powered by blists - more mailing lists