From: Michael Brown <mcb30@ipxe.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>
Cc: ipxe-devel@lists.ipxe.org, "László Érsek" <lersek@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [ipxe-devel] https booting
Date: Fri, 24 Jul 2020 17:19:38 +0100 [thread overview]
Message-ID: <411ac2fb-1f3e-28f0-5c9a-6ff0806cfbf7@ipxe.org> (raw)
In-Reply-To: <20200722141318.GJ2324845@redhat.com>
On 22/07/2020 15:13, Daniel P. Berrangé wrote:
> We could easily define etc/ipxe/https/{ciphers,cacerts} paths in a
> different format if better suited for iPXE. Libvirt can set the right
> path depending on whether its booting a VM with EDK2 vs legacy BIOS
The most useful for iPXE would probably be to expose the fw_cfg
mechanism as a URI scheme. This would give a general mechanism allowing
for use cases such as running a script provided by the host via e.g.
chain fw_cfg:///opt/org.example/script.ipxe
The ${crosscert} setting could then be pointed at a base URL within the
fw_cfg space, e.g.
#define CROSSCERT "fw_cfg:///etc/ipxe/crosscert/auto"
This would then work in the same way under either BIOS or UEFI (or other
custom firmware), would provide a feature with applicability broader
than just obtaining certificates, and would avoid any potential problems
from allocating enough RAM to parse every root certificate from iPXE's
fixed 512kB internal heap.
What do you think?
Michael
next prev parent reply other threads:[~2020-07-24 16:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 12:08 https booting Gerd Hoffmann
2020-07-22 12:23 ` Daniel P. Berrangé
2020-07-22 13:55 ` Gerd Hoffmann
2020-07-22 14:13 ` Daniel P. Berrangé
2020-07-22 18:47 ` Laszlo Ersek
2020-07-24 16:19 ` Michael Brown [this message]
2020-08-03 7:37 ` [ipxe-devel] " Gerd Hoffmann
2020-07-22 13:21 ` Michael Brown
2020-07-22 13:45 ` Michael Brown
2020-08-03 8:04 ` Gerd Hoffmann
2020-07-22 18:34 ` Laszlo Ersek
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=411ac2fb-1f3e-28f0-5c9a-6ff0806cfbf7@ipxe.org \
--to=mcb30@ipxe.org \
--cc=berrange@redhat.com \
--cc=ipxe-devel@lists.ipxe.org \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.