From: Christian Melki <christian.melki@t2data.com>
To: Ladislav Michl <ladis@linux-mips.org>, Alexander Dahl <ada@thorsis.com>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [RFC PATCH 0/2] openssl: Add more hw acceleration support options
Date: Wed, 4 Mar 2026 17:14:29 +0100 [thread overview]
Message-ID: <89bcb787-0d67-4781-9b0d-cb08e12db5d4@t2data.com> (raw)
In-Reply-To: <20260304120201.3180281-1-ada@thorsis.com>
On 3/4/26 1:01 PM, Alexander Dahl via ptxdist wrote:
> I was experimenting with crypto hardware acceleration on microchip at91
> sam9x60 based hardware [1] and stumbled over two things in ptxdist
> openssl package. Our usecases (for example lighttpd + TLS) seems not to
> benefit from kTLS, cryptodev, or AF_ALG on this platform, but I leave
> this here for reference if anyone wants to pick it up.
>
> The reaseon why it is marked RFC: the shared objects in
> /usr/lib/engines-3 are rather small (especially compared to
> /usr/lib/libcrypto.so.3), so maybe install all of them unconditionally
> with `install_tree()` instead?
>
> Note: openssl drops engine support with the upcoming 4.0 release.
> Support may come back with 4.1 as provider, but 4.0 will probably come
> without support for cryptodev and af_alg: See
> https://github.com/openssl/project/issues/1318 and linked tickets for
> details.
>
There is nothing wrong with this apart from pretty much the last section
as objection. Engine support is dead according to the openssl team,
weather the world likes it or not. If this can't be built/installed in
4.0, why not wait until 4.1 then?
I'm still super interested in how the world is going to cope without all
the engine support for all vendor whatnots that is out there.
Regards,
Christian
> Greets
> Alex
>
> [1] https://developerhelp.microchip.com/xwiki/bin/view/applications/linux4sam/faq/crypto-config/
>
> Alexander Dahl (2):
> openssl: Install cryptodev shared object to target
> openssl: Add option for AF_ALG support
>
> rules/openssl.in | 7 +++++++
> rules/openssl.make | 10 ++++++++++
> 2 files changed, 17 insertions(+)
>
>
> base-commit: 938919627b16d7e2a9558ce1316fb4e42245479c
prev parent reply other threads:[~2026-03-04 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 12:01 Alexander Dahl via ptxdist
2026-03-04 12:02 ` [ptxdist] [RFC PATCH 1/2] openssl: Install cryptodev shared object to target Alexander Dahl via ptxdist
2026-03-04 12:02 ` [ptxdist] [RFC PATCH 2/2] openssl: Add option for AF_ALG support Alexander Dahl via ptxdist
2026-03-04 16:14 ` Christian Melki [this message]
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=89bcb787-0d67-4781-9b0d-cb08e12db5d4@t2data.com \
--to=christian.melki@t2data.com \
--cc=ada@thorsis.com \
--cc=ladis@linux-mips.org \
--cc=ptxdist@pengutronix.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