From: Baoquan He <bhe@redhat.com>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: Coiby Xu <coxu@redhat.com>,
kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org,
Dave Young <dyoung@redhat.com>, Will Deacon <will@kernel.org>,
"Eric W . Biederman" <ebiederm@xmission.com>,
akpm@linux-foundation.org
Subject: Re: [PATCH v5 0/3] use more system keyrings to verify arm64 kdump kernel image signature
Date: Mon, 11 Apr 2022 09:13:32 +0800 [thread overview]
Message-ID: <YlOAvM4qpSlHczOd@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20220408085931.GW163591@kunlun.suse.cz>
On 04/08/22 at 10:59am, Michal Suchánek wrote:
> On Fri, Apr 08, 2022 at 03:17:19PM +0800, Baoquan He wrote:
> > Hi Coiby,
> >
> > On 04/01/22 at 09:31am, 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 patch set allows arm64 to use more system keyrings to verify kdump
> > > kernel image signature by making the existing code in x64 public.
> >
> > Thanks for updating. It would be great to tell why the problem is
> > met, then allow arm64 to use more system keyrings can solve it.
>
> The reason is that MOK keys are (if anywhere) linked to the secondary
> keyring, and only primary keyring is used on arm64.
Thanks for explaining. This is valuable information and should
be put into log for better understanding when reviewing or
reading code later.
_______________________________________________
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-11 1:15 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
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 [this message]
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=YlOAvM4qpSlHczOd@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=coxu@redhat.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).