From: Jordan <jorhand@linux.microsoft.com>
To: linux-integrity <linux-integrity@vger.kernel.org>
Cc: jarkko.sakkinen@linux.intel.com, mjg59@google.com
Subject: linux-tpmdd self signed kernel failing to boot with secreboot on
Date: Wed, 24 Apr 2019 11:30:07 -0700 [thread overview]
Message-ID: <f9ad2e46-e458-6c78-76da-b85db4601ee3@linux.microsoft.com> (raw)
Hello,
I am attempting to boot the linux-tpmdd kernel and look at the TCG 2
binary_bios_measurements.
Under the following circumstances my kernel will not boot:
* Secure boot enabled
* Booting with shim and grub2 from the Ubuntu 18 repos
* Kernel config is just taken from my ubuntu 18.04.2 install, and filled
in with `yes '' | make oldconfig`
* Kernel signed with my own generated key. Signed using sbsign, key is
enrolled in MOK.
* It seems to be going through the kernel's EFI stub (I see efi_printk
message "EFI: UEFI Secure Boot is enabled")
I have tried these same steps with the same configuration with the
mainline kernel and it boots fine.
I have traced kernel boot to the call to efi_exit_boot_services in
arch/x86/boot/compressed/eboot at which point execution terminates. I
see Matthew has made a couple changes in efi_main which calls exit_boot
(and in turn calls efi_exit_boot_services).
I am wondering if anyone else has seen this issue or might understand
better than me what is going on.
I would be happy to try to repro this issue with a more minimal config
if someone could point me to what steps to follow. I've tried it out on
a couple different machines with the same results.
Thanks,
Jordan
next reply other threads:[~2019-04-24 18:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 18:30 Jordan [this message]
2019-04-25 21:47 ` linux-tpmdd self signed kernel failing to boot with secreboot on Matthew Garrett
2019-04-29 15:30 ` Jordan Hand
2019-04-29 19:17 ` Matthew Garrett
2019-04-29 20:35 ` Jordan Hand
2019-04-29 22:50 ` Matthew Garrett
2019-04-30 16:28 ` Jordan Hand
2019-04-30 22:43 ` Matthew Garrett
2019-04-30 23:00 ` Jordan Hand
2019-04-30 23:24 ` Matthew Garrett
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=f9ad2e46-e458-6c78-76da-b85db4601ee3@linux.microsoft.com \
--to=jorhand@linux.microsoft.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-integrity@vger.kernel.org \
--cc=mjg59@google.com \
/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).