From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Sat, 9 May 2026 03:34:14 +0300 From: Vitaly Chikunov To: ALT Linux kernel packages development Message-ID: References: <20260506173722.1012394-1-egori@altlinux.org> <20260506173722.1012394-7-egori@altlinux.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20260506173722.1012394-7-egori@altlinux.org> Subject: Re: [d-kernel] [PATCH 6/6] config: Enable LOCK_DOWN_IN_EFI_SECURE_BOOT X-BeenThere: devel-kernel@lists.altlinux.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: ALT Linux kernel packages development List-Id: ALT Linux kernel packages development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 May 2026 00:34:14 -0000 Archived-At: List-Archive: List-Post: On Wed, May 06, 2026 at 08:37:22PM +0300, Egor Ignatov wrote: > Signed-off-by: Egor Ignatov Было бы неплохо в этом патче иметь небольшое обоснование, что это обязательно для прохождения shim-review для подписи shim для Secure Boot, со ссылкой: Link: https://github.com/rhboot/shim-review#how-does-your-signed-kernel-enforce-lockdown-when-your-system-runs-with-secure-boot-enabled > --- > config | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/config b/config > index 9aaf07ae98..596785caa3 100644 > --- a/config > +++ b/config > @@ -10132,6 +10132,7 @@ CONFIG_SECURITY_YAMA=y > CONFIG_SECURITY_SAFESETID=y > CONFIG_SECURITY_LOCKDOWN_LSM=y > CONFIG_SECURITY_LOCKDOWN_LSM_EARLY=y > +CONFIG_LOCK_DOWN_IN_EFI_SECURE_BOOT=y > CONFIG_LOCK_DOWN_KERNEL_FORCE_NONE=y > # CONFIG_LOCK_DOWN_KERNEL_FORCE_INTEGRITY is not set > # CONFIG_LOCK_DOWN_KERNEL_FORCE_CONFIDENTIALITY is not set > -- > 2.50.1 > > _______________________________________________ > devel-kernel mailing list > devel-kernel@lists.altlinux.org > https://lists.altlinux.org/mailman/listinfo/devel-kernel