From: Philipp Deppenwiese <zaolin.daisuki@gmail.com>
To: edk2-devel@lists.01.org
Subject: [OvmfPkg] Secure Boot issues
Date: Tue, 12 Jun 2018 15:12:01 +0200 [thread overview]
Message-ID: <fef206fe-393b-dd84-800c-a7330c494b6d@gmail.com> (raw)
Hey people,
We are experiencing issues with UEFI secure boot enabled
on UDK 2018 for the OvmfPkg.
Reproducible issue:
1) Add following code + files as dxe driver.
https://gist.github.com/zaolin/976d0d2ad68bcd05c10ffdb2530341fc
2) Build OvmfPkg with -DSECURE_BOOT_ENABLE=TRUE
3) Windows 10 boots and crashes in Qemu with a
/KMODE_EXCEPTION_NOT_HANDLED./
If we don't populate the keys or use Linux in with secure boot turned on
everything is totally fine.
Any suggestions ?
Best Regards, Philipp
next reply other threads:[~2018-06-12 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 13:12 Philipp Deppenwiese [this message]
2018-06-12 13:59 ` [OvmfPkg] Secure Boot issues Laszlo Ersek
2018-06-12 14:51 ` Philipp Deppenwiese
2018-06-12 18:14 ` Laszlo Ersek
2018-06-13 13:45 ` Philipp Deppenwiese
2018-06-13 19:21 ` Laszlo Ersek
2018-06-13 19:41 ` Philipp Deppenwiese
2018-06-13 21:18 ` Laszlo Ersek
2018-06-13 21:25 ` Philipp Deppenwiese
2018-06-14 17:29 ` Laszlo Ersek
2018-06-18 12:14 ` Philipp Deppenwiese
2018-06-18 12:30 ` 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-list 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=fef206fe-393b-dd84-800c-a7330c494b6d@gmail.com \
--to=devel@edk2.groups.io \
/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