Skip to content

Conversation

@gabrielssanches
Copy link
Contributor

Generates UEFI device tree files instead of doing outside of yocto.
This covers generation of UefiDefaultSecurityKeys.dts/dtbo
The minimal set of keys and certs is:

TEGRA_UEFI_PK_CERT
TEGRA_UEFI_KEK_1_CERT
TEGRA_UEFI_DB_1_KEY
TEGRA_UEFI_DB_1_CERT

tegra-flashtools-native: installs gen_uefi_keys_dts.sh

gen_uefi_keys_dts.sh is used for generating device tree
files for UEFI keys. This commit enables the generation
step automation by depending on this recipe.

Signed-off-by: Gabriel dos Santos Sanches <[email protected]>
Generates UEFI device tree files instead of doing outside of yocto.

This covers generation of UefiDefaultSecurityKeys.dts/dtbo only

The minimal set of keys and certs is:

TEGRA_UEFI_PK_CERT
TEGRA_UEFI_KEK_1_CERT
TEGRA_UEFI_DB_1_KEY
TEGRA_UEFI_DB_1_CERT

up to 3 KEK and DB certs may be provided.
see official documentation for more info.

Signed-off-by: Gabriel dos Santos Sanches <[email protected]>
@gabrielssanches
Copy link
Contributor Author

gabrielssanches commented Sep 23, 2025

There is an issue to be solved still.

it depends on cert-to-efi-sig-list which is provided by efitools
I brought https://github.com/Wind-River/meta-secure-core locally to cover that, but had to include 3 additional layers:

meta-perl
meta-secure-core-common
meta-efi-secure-boot
meta-signing-key

it is a bit too much in my opinion, but the alternative is to roll a meta-tegra efitool recipe (may be just focused on building cert-to-efi-sig-list)

let me know what are your thoughts on this

@madisongh
Copy link
Member

I'd prefer it if the existing recipe retains its current behavior by default, so as not to break builds that use the bbappend approach.

While automating the DTS file generation isn't a bad idea, I'm a bit worried that having a recipe do that generation would make it too easy to expose secrets, since users are apt to just check in the db_1.key and db_1.cert files into git as part of a layer.

As for the missing tool, we could add a recipe to build just the needed tool for this purpose.

@gabrielssanches
Copy link
Contributor Author

sounds like the right way to do it. I am on paternity leave until March 2026 😅 so it will have to wait

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants