linux-kernel - Re: [PATCH 0/2] Secure Boot lock down

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250716212925.GA14322@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
Date: Wed, 16 Jul 2025 14:29:25 -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
Subject: Re: [PATCH 0/2] Secure Boot lock down

Ping?

On Thu, Jun 26, 2025 at 03:10:37PM -0700, Hamza Mahfooz wrote:
> 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