public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Jason Dickens <jdickens@grammatech.com>
To: edk2-devel@lists.01.org
Subject: OVMF Secure Boot variable storage issue
Date: Thu, 6 Jul 2017 13:31:18 -0400	[thread overview]
Message-ID: <6703d38b-e99b-c11e-0126-ad24239dacee@grammatech.com> (raw)

All,

I'm trying to understand why the secure boot variables (PK, KEK, db, 
etc) when using the OVMF build are not retained across reboot? It seems 
that this code uses roughly the same SetVariable, GetVariable2 approach 
as say the PlatformConfig uses to store screen resolution (which is 
retained). Additionally, the NvVars file is being at least touched by 
the secure boot configuration. So why are none of the keys retained on 
the next reboot?

I know this was an issue in the past, but I haven't found the resolution?

Jason




             reply	other threads:[~2017-07-06 17:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 17:31 Jason Dickens [this message]
2017-07-06 18:30 ` OVMF Secure Boot variable storage issue Bill Paul
2017-07-06 18:55   ` Jason Dickens
2017-07-12 14:00     ` Konrad Rzeszutek Wilk
2017-07-06 19:08   ` Laszlo Ersek
2017-07-06 18:49 ` 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=6703d38b-e99b-c11e-0126-ad24239dacee@grammatech.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