From: "Rebecca Cran" <rebecca@bsdio.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Doug Flick <dougflick@microsoft.com>, Kun Qin <kuqin@microsoft.com>
Subject: [edk2-devel] Secure Boot: error enrolling dbx from uefi.org into dbxDefault (file is in wrong format?)
Date: Tue, 26 Nov 2024 18:32:56 -0700 [thread overview]
Message-ID: <b7bc26cb-a5ed-4711-aacc-9cf03d3d7a49@bsdio.com> (raw)
I'm working on Secure Boot support and noticed the dbxDefault variable
isn't being created: during boot I get the messages:
SecureBootFetchData: Invalid key format: 0
Content for dbxDefault not found
I'm using ArmPlatformPkg/SecureBootDefaultKeys.fdf.inc to add the data
to my firmware.
The problem appears to be this: at https://uefi.org/revocationlistfile
it says:
"These files are used to update the Secure Boot Forbidden Signature
Database, dbx. It contains the raw bytes passed in *Data to
SetVariable()... an EFI_VARIABLE_AUTHENTICATION_2 concatenated with the
new variable value. Example usage: SetVariable( "dbx",
EFI_IMAGE_SECURITY_DATABASE_GUID, NV+BS+RT+AT+AppendWrite,
dbxUpdateDotBin_sizeInBytes, *dbxUpdateDotBin_bytes). dbxupdate.bin
already contains a Microsoft KEK signature (encoded as specified by the
UEFI spec)."
But SecureBootFetchData calls RsaGetPublicKeyFromX509, which won't work
because the data is in the wrong format?
Looking at the files in the release from
https://github.com/microsoft/secureboot_objects it looks like they're
also in the format suitable for calling SetVariable, not for parsing as
X509.
Has anyone else come across this and knows of a solution?
--
Rebecca Cran
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120848): https://edk2.groups.io/g/devel/message/120848
Mute This Topic: https://groups.io/mt/109800343/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
reply other threads:[~2024-11-27 1:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b7bc26cb-a5ed-4711-aacc-9cf03d3d7a49@bsdio.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