From: Coiby Xu <coxu@redhat.com>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org,
Baoquan He <bhe@redhat.com>, Dave Young <dyoung@redhat.com>,
Will Deacon <will@kernel.org>,
"Eric W . Biederman" <ebiederm@xmission.com>,
Catalin Marinas <catalin.marinas@arm.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 3/3] arm64: kexec_file: use more system keyrings to verify kernel image signature
Date: Thu, 14 Apr 2022 09:44:46 +0800 [thread overview]
Message-ID: <20220414014446.tqopgaz2n3srwc6p@Rk> (raw)
In-Reply-To: <20220411085938.GA163591@kunlun.suse.cz>
On Mon, Apr 11, 2022 at 10:59:38AM +0200, Michal Suchánek wrote:
>On Fri, Apr 01, 2022 at 09:31:18AM +0800, Coiby Xu wrote:
>> Currently, a problem faced by arm64 is if a kernel image is signed by a
>> MOK key, loading it via the kexec_file_load() system call would be
>> rejected with the error "Lockdown: kexec: kexec of unsigned images is
>> restricted; see man kernel_lockdown.7".
>
>This is because image_verify_sig uses only the primary keyring that
>contains only kernel built-in keys to verify the kexec image.
>
>> This patch allows to verify arm64 kernel image signature using not only
>> .builtin_trusted_keys but also .platform and .secondary_trusted_key
>> keyring.
>>
>> Acked-by: Will Deacon <will@kernel.org>
>> Signed-off-by: Coiby Xu <coxu@redhat.com>
>> ---
>> arch/arm64/kernel/kexec_image.c | 4 +---
>> 1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/arch/arm64/kernel/kexec_image.c b/arch/arm64/kernel/kexec_image.c
>> index 9ec34690e255..51af1c22d6da 100644
>> --- a/arch/arm64/kernel/kexec_image.c
>> +++ b/arch/arm64/kernel/kexec_image.c
>> @@ -14,7 +14,6 @@
>> #include <linux/kexec.h>
>> #include <linux/pe.h>
>> #include <linux/string.h>
>> -#include <linux/verification.h>
>> #include <asm/byteorder.h>
>> #include <asm/cpufeature.h>
>> #include <asm/image.h>
>> @@ -133,8 +132,7 @@ static void *image_load(struct kimage *image,
>> #ifdef CONFIG_KEXEC_IMAGE_VERIFY_SIG
>> static int image_verify_sig(const char *kernel, unsigned long kernel_len)
>> {
>> - return verify_pefile_signature(kernel, kernel_len, NULL,
>> - VERIFYING_KEXEC_PE_SIGNATURE);
>> + return kexec_kernel_verify_pe_sig(kernel, kernel_len);
>> }
>> #endif
>
>You can eliminate image_verify_sig here aswell and directly assign
>kexec_kernel_verify_pe_sig to fops.
Good suggestions, thanks!
>
>Thanks
>
>Michal
>
--
Best regards,
Coiby
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-14 1:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 1:31 [PATCH v5 0/3] use more system keyrings to verify arm64 kdump kernel image signature Coiby Xu
2022-04-01 1:31 ` [PATCH v5 1/3] kexec: clean up arch_kexec_kernel_verify_sig Coiby Xu
2022-04-11 9:01 ` Michal Suchánek
2022-04-01 1:31 ` [PATCH v5 2/3] kexec, KEYS: make the code in bzImage64_verify_sig generic Coiby Xu
2022-04-11 8:54 ` Michal Suchánek
2022-04-14 1:46 ` Coiby Xu
2022-04-01 1:31 ` [PATCH v5 3/3] arm64: kexec_file: use more system keyrings to verify kernel image signature Coiby Xu
2022-04-11 8:59 ` Michal Suchánek
2022-04-14 1:44 ` Coiby Xu [this message]
2022-04-08 7:17 ` [PATCH v5 0/3] use more system keyrings to verify arm64 kdump " Baoquan He
2022-04-08 8:59 ` Michal Suchánek
2022-04-11 1:13 ` Baoquan He
2022-04-11 1:52 ` Coiby Xu
2022-04-11 8:43 ` Michal Suchánek
2022-04-13 9:32 ` Coiby Xu
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=20220414014446.tqopgaz2n3srwc6p@Rk \
--to=coxu@redhat.com \
--cc=bhe@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msuchanek@suse.de \
--cc=will@kernel.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox