From: Egor Ignatov <egori@altlinux.org>
To: devel-kernel@lists.altlinux.org
Subject: Re: [d-kernel] [PATCH 6/6] config: Enable LOCK_DOWN_IN_EFI_SECURE_BOOT
Date: Wed, 20 May 2026 15:29:12 +0300
Message-ID: <4ee211b7-b7a7-403a-8179-389e46542c1e@altlinux.org> (raw)
In-Reply-To: <af6AIf_7i1z13ztK@altlinux.org>
On 5/9/26 3:34 AM, Vitaly Chikunov wrote:
> On Wed, May 06, 2026 at 08:37:22PM +0300, Egor Ignatov wrote:
>> Signed-off-by: Egor Ignatov <egori@altlinux.org>
>
> Было бы неплохо в этом патче иметь небольшое обоснование, что это
> обязательно для прохождения 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
Согласен. Так же замечу, что это не только требование shim, но и
рекомендация Центр исследований безопасности системного программного
обеспечения [1].
[1] https://portal.linuxtesting.ru/LVCSecureBoot.html#4_3
>
>> ---
>> 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
> _______________________________________________
> devel-kernel mailing list
> devel-kernel@lists.altlinux.org
> https://lists.altlinux.org/mailman/listinfo/devel-kernel
--
Egor Ignatov
ALT Linux Team
next prev parent reply other threads:[~2026-05-20 12:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 17:37 [d-kernel] [PATCH 0/6] [7.0, 7.1] Lock down the kernel if booted in Secure Boot mode Egor Ignatov
2026-05-06 17:37 ` [d-kernel] [PATCH 1/6] mtd: phram, slram: Disable when the kernel is locked down Egor Ignatov
2026-05-08 23:43 ` Vitaly Chikunov
2026-05-06 17:37 ` [d-kernel] [PATCH 2/6] security: lockdown: expose security_lock_kernel_down function Egor Ignatov
2026-05-09 0:20 ` Vitaly Chikunov
2026-05-20 12:25 ` Egor Ignatov
2026-05-06 17:37 ` [d-kernel] [PATCH 3/6] efi: Add an EFI_SECURE_BOOT flag to indicate secure boot mode Egor Ignatov
2026-05-06 17:37 ` [d-kernel] [PATCH 4/6] efi: Lock down the kernel if booted in " Egor Ignatov
2026-05-09 0:24 ` Vitaly Chikunov
2026-05-20 12:28 ` Egor Ignatov
2026-05-06 17:37 ` [d-kernel] [PATCH 5/6] efi: determine and pass Secure Boot state via FDT Egor Ignatov
2026-05-09 0:28 ` Vitaly Chikunov
2026-05-20 12:29 ` Egor Ignatov
2026-05-06 17:37 ` [d-kernel] [PATCH 6/6] config: Enable LOCK_DOWN_IN_EFI_SECURE_BOOT Egor Ignatov
2026-05-09 0:34 ` Vitaly Chikunov
2026-05-20 12:29 ` Egor Ignatov [this message]
2026-05-08 23:01 ` [d-kernel] [PATCH 0/6] [7.0, 7.1] Lock down the kernel if booted in Secure Boot mode Vitaly Chikunov
2026-05-20 12:29 ` Egor Ignatov
2026-05-20 16:32 ` Vitaly Chikunov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ee211b7-b7a7-403a-8179-389e46542c1e@altlinux.org \
--to=egori@altlinux.org \
--cc=devel-kernel@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux kernel packages development
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel-kernel/0 devel-kernel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel-kernel devel-kernel/ http://lore.altlinux.org/devel-kernel \
devel-kernel@altlinux.org devel-kernel@altlinux.ru devel-kernel@altlinux.com
public-inbox-index devel-kernel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel-kernel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git