From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Moessbauer,
Felix (FT RPD CED OES-DE)" <felix.moessbauer@siemens.com>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Cc: Sai Sree Kartheek Adivi <s-adivi@ti.com>,
"Gylstorff,
Quirin (FT RPD CED OES-DE)" <quirin.gylstorff@siemens.com>,
"Heinisch,
Alexander (FT RPD CED SES-AT)" <alexander.heinisch@siemens.com>
Subject: Re: [cip-dev] [isar-cip-core][PATCH v2 1/7] secure-boot-efi-keys: Add recipe to create EFI certificates
Date: Mon, 14 Sep 2026 09:16:05 +0200 [thread overview]
Message-ID: <e5ade92e-e7ac-49b0-ab7e-7a4aa6723fe0@siemens.com> (raw)
In-Reply-To: <6f0cc5409fe4c6e5d1b8e8907c2ba2091ae90f8e.camel@siemens.com>
On 14.09.26 08:59, Moessbauer, Felix (FT RPD CED OES-DE) wrote:
> On Wed, 2026-08-26 at 17:20 +0200, Jan Kiszka via lists.cip-project.org
> wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> This recipe allows to derive the PK, KEK and db values from a single
>> signing key as we are using for demonstration/testing purposes and
>> simple scenarios. The recipe provides abstract "secure-boot-efi-certs"
>> which could also be offered by an alternative recipe/package that picks
>> up differently generated certificates and/or a proper hierarchy.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>> .../single-key-to-efi-certs_0.1.bb | 41 +++++++++++++++++++
>> 1 file changed, 41 insertions(+)
>> create mode 100644 recipes-devtools/secure-boot-efi-certs/single-key-to-efi-certs_0.1.bb
>>
>> diff --git a/recipes-devtools/secure-boot-efi-certs/single-key-to-efi-certs_0.1.bb b/recipes-devtools/secure-boot-efi-certs/single-key-to-efi-certs_0.1.bb
>> new file mode 100644
>> index 00000000..01d27041
>> --- /dev/null
>> +++ b/recipes-devtools/secure-boot-efi-certs/single-key-to-efi-certs_0.1.bb
>> @@ -0,0 +1,41 @@
>> +#
>> +# CIP Core, generic profile
>> +#
>> +# Copyright (c) Siemens AG, 2026
>> +#
>> +# Authors:
>> +# Jan Kiszka <jan.kiszka@siemens.com>
>> +#
>> +# SPDX-License-Identifier: MIT
>> +#
>> +
>> +inherit dpkg
>
> Hi, please either use dpkg-raw, or set DPKG_ARCH = "all", as
> this package does not depend on the architecture of the target.
>
Added
DPKG_ARCH = "all"
in next.
Thanks,
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
next prev parent reply other threads:[~2026-09-14 7:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 15:20 [isar-cip-core][PATCH v2 0/7] Provide measured boot via fTPM for arm64, early deploy EFI certificates Jan Kiszka
2026-08-26 15:20 ` [isar-cip-core][PATCH v2 1/7] secure-boot-efi-keys: Add recipe to create " Jan Kiszka
2026-09-14 6:59 ` [cip-dev] " MOESSBAUER, Felix
2026-09-14 7:16 ` Jan Kiszka [this message]
2026-08-26 15:20 ` [isar-cip-core][PATCH v2 2/7] cip-initramfs-functions: Add secure_boot_enabled helper Jan Kiszka
2026-08-26 15:20 ` [isar-cip-core][PATCH v2 3/7] cip-core-initramfs: Automatically deploy EFI secure boot certificates on first boot Jan Kiszka
2026-09-23 9:36 ` Heinisch, Alexander (FT RPD CED SES-AT)
2026-08-26 15:20 ` [isar-cip-core][PATCH v2 4/7] u-boot: Add patches to enable measured boot with fTPM Jan Kiszka
2026-09-08 16:41 ` [isar-cip-core][PATCH v3 " Jan Kiszka
2026-09-14 6:25 ` [isar-cip-core][PATCH v4 " Jan Kiszka
2026-08-26 15:20 ` [isar-cip-core][PATCH v2 5/7] u-boot: Refactor ftpm-stmm.cfg to enable measured boot for all Jan Kiszka
2026-08-26 15:20 ` [isar-cip-core][PATCH v2 6/7] u-boot: Drop obsolete config workaround Jan Kiszka
2026-08-26 15:20 ` [isar-cip-core][PATCH v2 7/7] initramfs-crypt-hook: Prevent encryption without secure boot Jan Kiszka
2026-08-27 7:44 ` [isar-cip-core][PATCH v2 8/7] doc: Update README.secureboot regarding recent deployment enhancements Jan Kiszka
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=e5ade92e-e7ac-49b0-ab7e-7a4aa6723fe0@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=alexander.heinisch@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=felix.moessbauer@siemens.com \
--cc=quirin.gylstorff@siemens.com \
--cc=s-adivi@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.