From: Quentin Schulz <quentin.schulz@cherry.de>
To: Peter Robinson <pbrobinson@gmail.com>,
Quentin Schulz <foss+uboot@0leil.net>
Cc: u-boot@lists.denx.de, Tom Rini <trini@konsulko.com>,
Aristo Chen <jj251510319013@gmail.com>,
Rasmus Villemoes <ravi@prevas.dk>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
Simon Glass <sjg@chromium.org>,
Paul HENRYS <paul.henrys_ext@softathome.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Shiji Yang <yangshiji66@outlook.com>,
Anton Moryakov <ant.v.moryakov@gmail.com>,
Alper Nebi Yasak <alpernebiyasak@gmail.com>,
Alice Guo <alice.guo@nxp.com>, Bryan Brattlof <bb@ti.com>
Subject: Re: [PATCH 3/3] tools: binman: fit: add support for OpenSSL engines
Date: Mon, 3 Nov 2025 17:47:50 +0100 [thread overview]
Message-ID: <d7173975-9308-4767-80d3-3472f9873dda@cherry.de> (raw)
In-Reply-To: <CALeDE9MYi2+u_ek1Rapmzx2_T9uE_cQcH8paKgxKwZjtGJ2gzg@mail.gmail.com>
Hi Peter,
On 11/3/25 5:21 PM, Peter Robinson wrote:
> Hey Quentin,
>
>> This adds support for using an OpenSSL engine for signing a FIT image.
>> To use it, one should set the fit,sign-engine property at the FIT node
>> level with the engine to use. This will in turn call mkimage with the -N
>> option.
>
> Just to be aware this should likely be a OpenSSL provider, engines in
> OpenSSL are deprecated and due to be removed in 4.0. A lot of distros
> are already dropping support for engines. There's a patch [1] adding
> support for Providers support to U-Boot, I suspect we shouldn't be
> adding more deps on the Engine support. OpenSSL 4 is due in March.
>
There is no plan (yet?) migrating my employer's engine to a provider, so
I have no interest in doing that.
Additionally, Tom said[1] that LibreSSL isn't going the OpenSSL route so
engines probably are here to stay?
Also, OpenSSL 3.5 (LTS) is supported until mid-2030.
Cheers,
Quentin
[1]
https://lore.kernel.org/u-boot/20251031-binman-engine-v1-0-c13c1b5dac43@cherry.de/T/#m8002ea155864cf8d1ab2b8bb16b997089f4fac0e
next prev parent reply other threads:[~2025-11-03 16:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 15:22 [PATCH 0/3] fit: allow signing with only an engine_id Quentin Schulz
2025-10-31 15:22 ` [PATCH 1/3] fit: support " Quentin Schulz
2025-11-02 19:53 ` Simon Glass
2025-11-11 10:10 ` Wolfgang Wallner
2025-10-31 15:22 ` [PATCH 2/3] tools: binman: mkimage: add support for passing the engine Quentin Schulz
2025-11-02 19:53 ` Simon Glass
2025-11-03 12:13 ` Quentin Schulz
2025-11-03 14:17 ` Tom Rini
2025-11-03 14:21 ` Quentin Schulz
2025-11-03 14:52 ` Simon Glass
2025-11-11 10:11 ` Wolfgang Wallner
2025-10-31 15:23 ` [PATCH 3/3] tools: binman: fit: add support for OpenSSL engines Quentin Schulz
2025-11-02 19:53 ` Simon Glass
2025-11-03 16:21 ` Peter Robinson
2025-11-03 16:47 ` Quentin Schulz [this message]
2025-11-11 10:14 ` Wolfgang Wallner
2025-11-17 15:18 ` Peter Robinson
2025-11-17 15:38 ` Tom Rini
2025-11-17 16:09 ` Quentin Schulz
2025-11-11 10:12 ` Wolfgang Wallner
2025-11-11 10:10 ` [PATCH 0/3] fit: allow signing with only an engine_id Wolfgang Wallner
2025-11-11 11:22 ` Quentin Schulz
2025-11-11 14:49 ` Wolfgang Wallner
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=d7173975-9308-4767-80d3-3472f9873dda@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=alice.guo@nxp.com \
--cc=alpernebiyasak@gmail.com \
--cc=ant.v.moryakov@gmail.com \
--cc=bb@ti.com \
--cc=foss+uboot@0leil.net \
--cc=jj251510319013@gmail.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=paul.henrys_ext@softathome.com \
--cc=pbrobinson@gmail.com \
--cc=ravi@prevas.dk \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
--cc=yangshiji66@outlook.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox