From: "Park, Kyung Min" <kyung.min.park@intel.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Secureboot enable with OVMF
Date: Thu, 13 Dec 2018 01:25:30 +0000 [thread overview]
Message-ID: <3658BA65DD26AF4BA909BEB2C6DF6181962783D2@ORSMSX102.amr.corp.intel.com> (raw)
Hi,
I'm trying to enable the secureboot with OVMF. I followed the steps as below.
But When I executed LockDown.efi, it gives me an error which says, "Failed to enroll PK: 26".
According to UEFI spec, the 26 means EFI_SECURITY_VIOLATION, but I don't understand why I got this error.
Before I ran the LockDown.efi, the secureboot was disabled by default and the PK key was not enrolled.
1. Build OVMF with secureboot enable
https://wiki.ubuntu.com/UEFI/EDK2
2. Generate/Execute LockDown.efi to enroll PK/KEK/DB keys
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/efitools.git
I would appreciate any useful information about this error.
Thanks,
Kyung Min
next reply other threads:[~2018-12-13 1:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 1:25 Park, Kyung Min [this message]
2018-12-13 10:49 ` Secureboot enable with OVMF Laszlo Ersek
2018-12-16 21:49 ` Park, Kyung Min
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=3658BA65DD26AF4BA909BEB2C6DF6181962783D2@ORSMSX102.amr.corp.intel.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