public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: Eddie Kovsky <ekovsky@redhat.com>,
	Mattijs Korpershoek <mkorpershoek@kernel.org>
Cc: Quentin Schulz <quentin.schulz@cherry.de>,
	Tom Rini <trini@konsulko.com>, Tobias Olausson <tobias@eub.se>,
	Paul HENRYS <paul.henrys_ext@softathome.com>,
	Simon Glass <sjg@chromium.org>, Jan Stancek <jstancek@redhat.com>,
	Enric Balletbo i Serra <eballetb@redhat.com>,
	a.fatoum@pengutronix.de, mark.kettenis@xs4all.nl,
	u-boot@lists.denx.de
Subject: Re: [PATCH v2] Add support for OpenSSL Provider API
Date: Mon, 05 Jan 2026 10:36:04 +0100	[thread overview]
Message-ID: <87zf6sflkr.fsf@kernel.org> (raw)
In-Reply-To: <aUmB_fvpK1macga7@daedalus>

On Mon, Dec 22, 2025 at 10:38, Eddie Kovsky <ekovsky@redhat.com> wrote:

> On 12/11/25, Mattijs Korpershoek wrote:
>> Hi Eddie,
>> 
>> Thank you for working on this. It would be really nice if we could build
>> U-Boot on more recent Linux distros without bridge packages such as
>> openssl-devel-engine.
>> 
>> 
>> I also don't linke this double negative.
>> As you already shared, Linux solved this via:
>> 
>> #if OPENSSL_VERSION_MAJOR >= 3
>> 
>> Why can't we have something similar?
>> See: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=558bdc45dfb2669e1741384a0c80be9c82fa052c
>> 
>
> Hi Mattijs
>
> Yes, we could also implement it this way with the extra USE_PKCS11_XXX
> symbol. Jan's original patch I based my work on does something similar,
> and I perhaps oversimplified it.

In my experience, when porting things from the Linux kernel into U-Boot,
we try to keep the code as similar as possible. This helps reducing
maintainance burden.

Sometimes, we can't do that. In that case, we should explain why.

Do we have a strong reason for *not* reusing OPENSSL_VERSION_MAJOR with
USE_PKCS11_XXX ?

[...]

>> >> 
>> >
>> > It's not the prettiest code. But I'm trying to be very conservative
>> > in making these changes so that no one's workflow is disrupted.
>> > Developers should be able to build U-Boot with the latest OpenSSL
>> > without impacting developers who are in environments utilizing the
>> > Engine API. The goal here is to preserve feature parity between the two
>> > APIs. Adding support for custom Providers is outside the scope of this
>> > change, but could certainly be added later.
>> 
>> I'd be in favor to drop CONFIG_OPENSSL_NO_DEPRECATED all together and
>> just use "#if OPENSSL_VERSION_MAJOR >= 3".
>> 
>> Tom, or anyone else, is there a particular` reason for gating this in a
>> Kconfig ?
>> 
>> The oldest Ubuntu version that seems supported (22.04) already has
>> OpenSSL version 3:
>> 
>> $ podman run -it /bin/bash ubuntu:22.04
>> root@6dc347676b8a:~# apt update && apt install -y openssl
>> root@6dc347676b8a:~# openssl version
>> OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)
>> 
>
> I assumed that we would want this to be an explicit config option, but
> logically there is no reason that it has to be. I'd be happy to spin up
> a v3 if there's agreement that the Kconfig isn't needed.

Tom, do you have an opinion on this? It seems you are listed as
maintainer for this (THE REST).

>
> Eddie

  reply	other threads:[~2026-01-05  9:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27 19:58 [PATCH v2] Add support for OpenSSL Provider API Eddie Kovsky
2025-11-17 15:56 ` Quentin Schulz
2025-11-21 18:16   ` Eddie Kovsky
2025-12-11  8:23     ` Mattijs Korpershoek
2025-12-22 17:38       ` Eddie Kovsky
2026-01-05  9:36         ` Mattijs Korpershoek [this message]
2026-01-06  0:33           ` Tom Rini
2026-01-16 19:00             ` Eddie Kovsky
2026-01-16 21:04               ` Tom Rini

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=87zf6sflkr.fsf@kernel.org \
    --to=mkorpershoek@kernel.org \
    --cc=a.fatoum@pengutronix.de \
    --cc=eballetb@redhat.com \
    --cc=ekovsky@redhat.com \
    --cc=jstancek@redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=paul.henrys_ext@softathome.com \
    --cc=quentin.schulz@cherry.de \
    --cc=sjg@chromium.org \
    --cc=tobias@eub.se \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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