linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@google.com>
To: Jordan Hand <jorhand@linux.microsoft.com>
Cc: linux-integrity <linux-integrity@vger.kernel.org>,
	Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Subject: Re: linux-tpmdd self signed kernel failing to boot with secreboot on
Date: Mon, 29 Apr 2019 12:17:09 -0700	[thread overview]
Message-ID: <CACdnJusXEq=7LXB=Ry0zH4CTRkQLHPC+5DnP07yXi0TNPeCYTw@mail.gmail.com> (raw)
In-Reply-To: <6373c67f-ea2f-ae1d-0343-4bb774f1d52f@linux.microsoft.com>

On Mon, Apr 29, 2019 at 8:31 AM Jordan Hand <jorhand@linux.microsoft.com> wrote:
>
> On 4/25/19 2:47 PM, Matthew Garrett wrote:
> > On Wed, Apr 24, 2019 at 11:30 AM 'Jordan' via mjg59 <mjg59@google.com> wrote:
> >> Under the following circumstances my kernel will not boot:
> >
> > Will it boot under other circumstances (ie, if you disable Secure
> > Boot, does it work fine with the patches?)
>
> Yes it works fine if secure boot is disabled.

That is… very strange. Disabling secure boot will change the contents
of PCR7, but I can't think of any reason that would matter. What
hardware is this on?

  reply	other threads:[~2019-04-29 19:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 18:30 linux-tpmdd self signed kernel failing to boot with secreboot on Jordan
2019-04-25 21:47 ` Matthew Garrett
2019-04-29 15:30   ` Jordan Hand
2019-04-29 19:17     ` Matthew Garrett [this message]
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='CACdnJusXEq=7LXB=Ry0zH4CTRkQLHPC+5DnP07yXi0TNPeCYTw@mail.gmail.com' \
    --to=mjg59@google.com \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=jorhand@linux.microsoft.com \
    --cc=linux-integrity@vger.kernel.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).