From: Daniel Kiper <daniel.kiper@oracle.com>
To: "Bill Jacobs (billjac)" <billjac@cisco.com>
Cc: "xen-users@lists.xen.org" <xen-users@lists.xen.org>,
"george.dunlap@citrix.com" <george.dunlap@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-users] UEFI Secure Boot Xen 4.9
Date: Fri, 13 Oct 2017 10:09:28 +0200 [thread overview]
Message-ID: <20171013080928.GZ7593@olila.local.net-space.pl> (raw)
In-Reply-To: <60bebfbfb4434a5f81587641d1b70302@XCH-RTP-007.cisco.com>
On Thu, Oct 12, 2017 at 05:03:13PM +0000, Bill Jacobs (billjac) wrote:
> Hi
> What is the status of creating a shim to abstract secure boot
> signing for Xen (to leverage MSFT 3rd party, e.g)?
xen.efi works with shim itself out of the box. If you wish
to use shim and GRUB2 to load Xen you have to look at these
RFC patch series:
- https://lists.xen.org/archives/html/xen-devel/2017-07/msg00982.html
- https://lists.xen.org/archives/html/xen-devel/2017-07/msg00985.html
I am slowly going back to this work. So, I hope that it will
be taken into Xen 4.11 or so.
Daniel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-10-13 8:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <adcea6ce93c54bc6b80d68c5721cc187@XCH-RTP-007.cisco.com>
[not found] ` <CAFLBxZa8EDduCpRXqmLdUDRC-5xz2NiwZQxwUUDbjXD7Q8gCDw@mail.gmail.com>
2017-05-15 13:12 ` [Xen-users] UEFI Secure Boot Xen 4.9 Daniel Kiper
2017-05-15 19:09 ` Bill Jacobs (billjac)
2017-05-16 11:04 ` Daniel Kiper
2017-08-23 3:01 ` Tamas K Lengyel
2017-08-29 20:01 ` Daniel Kiper
2017-08-30 16:16 ` Tamas K Lengyel
2017-09-04 12:40 ` Daniel Kiper
2017-09-05 16:26 ` Tamas K Lengyel
2017-09-18 15:24 ` Tamas K Lengyel
2017-09-19 12:19 ` Daniel Kiper
2017-10-12 17:03 ` Bill Jacobs (billjac)
2017-10-13 8:09 ` Daniel Kiper [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=20171013080928.GZ7593@olila.local.net-space.pl \
--to=daniel.kiper@oracle.com \
--cc=billjac@cisco.com \
--cc=george.dunlap@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@lists.xen.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.