From: Denis OSTERLAND-HEIM <denis.osterland@diehl.com>
To: "Freihofer, Adrian" <adrian.freihofer@siemens.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: AW: [EXT] [OE-core] [PATCH v7 11/20] kernel-fit-image.bbclass: add a new FIT image implementation
Date: Fri, 5 Dec 2025 06:46:04 +0000 [thread overview]
Message-ID: <bcfe72105d0a44efa7ed065fc58d0fea@diehl.com> (raw)
In-Reply-To: <AS1PR10MB5724417B1328B03E60727C4E8EA6A@AS1PR10MB5724.EURPRD10.PROD.OUTLOOK.COM>
Hi Adrian,
Thanks for your reply.
I was not aware of a version from meta-oe, but that fits my needs.
You are right, it is strange that there are two variants.
On the other hand, oe-core does not have the signing class either and therefor must not be compatible.
Maybe one day meta-oe fitimage class inherits from kernel-fit-image class and adds the compatibility for signing class.
Your resigning idea looks doable, but I would prefer to not introduce a stub key.
Regards, Denis
-----Ursprüngliche Nachricht-----
Von: Freihofer, Adrian <adrian.freihofer@siemens.com>
Gesendet: Donnerstag, 4. Dezember 2025 16:02
An: Denis OSTERLAND-HEIM <denis.osterland@diehl.com>; openembedded-core@lists.openembedded.org
Betreff: [EXT] Re: [EXT] [OE-core] [PATCH v7 11/20] kernel-fit-image.bbclass: add a new FIT image implementation
[EXTERNAL EMAIL]
Hi Denis
I'm not entirely sure which FIT image implementation you are using: the one from oe-core or the one from meta-openembedded. Since you are asking me personally, I assume it is the one from oe-core.
I suspect that the classes from meta-openembedded are not compatible with the FIT image implementation in oe-core. But I'm probably not the right person to answer this question, as I don't even understand why a second FIT image implementation was necessary instead of improving the one in oe-core. From my perspective, it would probably be better to extend the run_mkimage_sign function in oe-core with PKCS#11 support than to maintain a second FIT image implementation in meta-openembedded.
Another approach is to perform the signing within bitbake using a key from a file. Signing with a more secure PKCS#11 backend can be performed as a re-signing, which is done independently of bitbake as the final step in the release process.
Regards,
Adrian
Diehl Metering GmbH, Donaustrasse 120, 90451 Nuernberg
Sitz der Gesellschaft: Ansbach, Registergericht: Ansbach HRB 69
Geschaeftsfuehrer: Dr. Christof Bosbach (Sprecher), Dipl.-Dolm. Annette Geuther, Dipl.-Kfm. Reiner Edel, Jean-Claude Luttringer
Bitte denken Sie an die Umwelt, bevor Sie diese E-Mail drucken. Diese E-Mail kann vertrauliche Informationen enthalten. Sollten die in dieser E-Mail enthaltenen Informationen nicht für Sie bestimmt sein, informieren Sie bitte unverzueglich den Absender per E-Mail und loeschen Sie diese E-Mail in Ihrem System. Jede unberechtigte Form der Reproduktion, Bekanntgabe, Aenderung, Verteilung und/oder Publikation dieser E-Mail ist strengstens untersagt. Informationen zum Datenschutz finden Sie auf unserer Homepage<https://www.diehl.com/metering/de/impressum-und-rechtliche-hinweise/>.
Before printing, think about environmental responsibility.This message may contain confidential information. If you are not authorized to receive this information please advise the sender immediately by reply e-mail and delete this message without making any copies. Any form of unauthorized use, publication, reproduction, copying or disclosure of the e-mail is not permitted. Information about data protection can be found on our homepage<https://www.diehl.com/metering/en/data-protection/>.
next prev parent reply other threads:[~2025-12-05 6:46 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 8:23 [PATCH v7 00/20] FIT image improvements AdrianF
2025-06-03 8:23 ` [PATCH v7 01/20] devicetree: minor improvements AdrianF
2025-06-03 8:23 ` [PATCH v7 02/20] oe-selftest: add new ext dtb recipe AdrianF
2025-06-03 8:23 ` [PATCH v7 03/20] oe-selftest: fitimage: test external dtb AdrianF
2025-06-03 8:23 ` [PATCH v7 04/20] oe-selftest: fitimage: test FIT_CONF_PREFIX AdrianF
2025-06-03 8:23 ` [PATCH v7 05/20] oe-selftest: fitimage: test FIT_CONF_DEFAULT_DTB AdrianF
2025-06-03 8:23 ` [PATCH v7 06/20] kernel-signing-keys-native: refactor key generation into a new recipe AdrianF
2025-06-03 8:23 ` [PATCH v7 07/20] maintainers: add myself for kernel-signing-keys-native AdrianF
2025-06-03 8:23 ` [PATCH v7 08/20] oe-selftest: fitimage: cleanup FIT_GENERATE_KEYS AdrianF
2025-06-03 8:23 ` [PATCH v7 09/20] kernel-fitimage: refactor order in its AdrianF
2025-06-03 8:23 ` [PATCH v7 10/20] kernel-uboot.bbclass: do not require the kernel build folder AdrianF
2025-06-03 8:23 ` [PATCH v7 11/20] kernel-fit-image.bbclass: add a new FIT image implementation AdrianF
2025-12-04 14:04 ` AW: [EXT] [OE-core] " Denis OSTERLAND-HEIM
2025-12-04 15:01 ` Freihofer, Adrian
2025-12-05 6:46 ` Denis OSTERLAND-HEIM [this message]
2025-06-03 8:23 ` [PATCH v7 12/20] maintainers: add myself for linux-yocto-fitimage AdrianF
2025-06-03 8:23 ` [PATCH v7 13/20] oe-selftest: fitimage: add tests for fitimage.py AdrianF
2025-06-03 8:23 ` [PATCH v7 14/20] oe-selftest: fitimage: support new FIT recipe as well AdrianF
2025-06-03 8:23 ` [PATCH v7 15/20] oe-selftest: fitimage: run all tests for both FIT implementations AdrianF
2025-06-03 8:23 ` [PATCH v7 16/20] oe-selftest: fitimage refactor classes AdrianF
2025-06-03 8:23 ` [PATCH v7 17/20] kernel-fitimage: re-write its code in Python AdrianF
2025-06-03 8:23 ` [PATCH v7 18/20] oe-selftest: fitimage: remove kernel-fitimage tests AdrianF
2025-06-03 8:23 ` [PATCH v7 19/20] kernel.bbclass: remove support for type fitImage AdrianF
2025-06-03 8:23 ` [PATCH v7 20/20] kernel-fitimage.bbclass: remove it AdrianF
2025-06-03 10:48 ` [OE-core] [PATCH v7 00/20] FIT image improvements Richard Purdie
2025-06-03 13:35 ` Freihofer, Adrian
2025-06-03 14:07 ` Richard Purdie
[not found] ` <18458D867A23466E.18429@lists.openembedded.org>
2025-06-04 7:12 ` Richard Purdie
2025-06-04 7:42 ` Freihofer, Adrian
[not found] ` <184582AE5B84DD18.18429@lists.openembedded.org>
2025-06-03 14:02 ` Richard Purdie
2025-06-04 11:13 ` Bruce Ashfield
2025-06-06 10:29 ` Francesco Dolcini
2025-06-06 14:11 ` Freihofer, Adrian
2025-06-06 15:52 ` [meta-ti] " Denys Dmytriyenko
2025-06-06 16:38 ` Freihofer, Adrian
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=bcfe72105d0a44efa7ed065fc58d0fea@diehl.com \
--to=denis.osterland@diehl.com \
--cc=adrian.freihofer@siemens.com \
--cc=openembedded-core@lists.openembedded.org \
/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.