From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <eduardo@habkost.net>,
Cole Robinson <crobinso@redhat.com>
Subject: Re: secure boot & direct kernel load (was: Re: [PATCH] x86/loader: only patch linux kernels)
Date: Mon, 15 Apr 2024 14:48:03 +0100 [thread overview]
Message-ID: <Zh0wExsBiH4NxLcn@redhat.com> (raw)
In-Reply-To: <asxsrqicnilb5wszzz23ebuidyqacmasb4ggtflcksdlufrspc@23x4k2gqge6r>
On Mon, Apr 15, 2024 at 03:30:32PM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > > Options I see:
> > >
> > > (a) Stop using direct kernel boot, let virt-install & other tools
> > > create vfat boot media with shim+kernel+initrd instead.
> > >
> > > (b) Enroll the distro signing keys in the efi variable store, so
> > > booting the kernel without shim.efi works.
> > >
> > > (c) Add support for loading shim to qemu (and ovmf), for example
> > > with a new '-shim' command line option which stores shim.efi
> > > in some new fw_cfg file.
> >
> > The problem with this is that now virt-install has to actually
> > find the correct a shim.efi binary. It is already somewhat hard
> > to find a suitable kerenl+initrd binary, and AFAIK, the places
> > where we get these binaries don't have shim.efi alongside.
> >
> > eg for RHEL/Fedora we grab kernel+initrd from the pxeboot dir:
> >
> > https://fedora.mirrorservice.org/fedora/linux/development/rawhide/Everything/x86_64/os/images/pxeboot/
>
> shim is https://fedora.mirrorservice.org/fedora/linux/development/rawhide/Everything/x86_64/os/EFI/BOOT/BOOTX64.EFI
>
> > In various forums we have discussed adding the secureboot
> > certs to the libosinfo database, so that we can have a
> > customized EFI varstore with minimized certs, even for the
> > ISO / HDD boot scenario.
>
> Well. It's not that easy unfortunately. At least the "minimized certs"
> part. shim often is signed with the microsoft keys only, so you can't
> drop that without rendering the install.iso unbootable.
>
> Only adding the distro certs without removing the microsoft certs works
> of course.
In that scenario libosinfo would report that the given OS
requires both the microsoft & $distro certs to be
enrolled.
Only if shim were signed by the $distro certs, would
libosifo omit reporting the microsoft certs.
Basically libosinfo would have to report whatever set
of 'n' certs are required to make boot work.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2024-04-15 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 7:21 [PATCH] x86/loader: only patch linux kernels Gerd Hoffmann
2024-04-10 7:26 ` Michael S. Tsirkin
2024-04-10 10:35 ` secure boot & direct kernel load (was: Re: [PATCH] x86/loader: only patch linux kernels) Gerd Hoffmann
2024-04-10 11:10 ` Michael S. Tsirkin
2024-04-10 11:52 ` Gerd Hoffmann
2024-04-10 15:01 ` Gerd Hoffmann
2024-04-15 11:59 ` Daniel P. Berrangé
2024-04-15 13:30 ` Gerd Hoffmann
2024-04-15 13:48 ` Daniel P. Berrangé [this message]
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=Zh0wExsBiH4NxLcn@redhat.com \
--to=berrange@redhat.com \
--cc=crobinso@redhat.com \
--cc=eduardo@habkost.net \
--cc=kraxel@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).