Re: [ptxdist] [RFC PATCH 1/2] openssl: Install cryptodev shared object to target

[Ladislav Michl <oss-lists@triops.cz>]

On Mon, Mar 09, 2026 at 08:35:51AM +0100, Alexander Dahl via ptxdist wrote:
> Hei hei,
> 
> Am Wed, Mar 04, 2026 at 01:02:00PM +0100 schrieb Alexander Dahl via ptxdist:
> > Recent openssl 3.5.5 produced this output on target:
> > 
> >     $ openssl engine -t -c -engine devcrypto
> >     200092B6:error:12800067:DSO support routines:dlfcn_load:could not load the shared library:crypto/dso/dso_dlfcn.c:115:filename(/usr/lib/engines-3/devcrypto.so): /usr/lib/engines-3/devcrypto.so: cannot open shared object file: No such file or directory
> >     200092B6:error:12800067:DSO support routines:DSO_load:could not load the shared library:crypto/dso/dso_lib.c:147:
> >     200092B6:error:13000084:engine routines:dynamic_load:dso not found:crypto/engine/eng_dyn.c:429:
> >     200092B6:error:13000074:engine routines:ENGINE_by_id:no such engine:crypto/engine/eng_list.c:470:id=devcrypto
> > 
> > Signed-off-by: Alexander Dahl <ada@thorsis.com>
> > ---
> >  rules/openssl.make | 5 +++++
> >  1 file changed, 5 insertions(+)
> > 
> > diff --git a/rules/openssl.make b/rules/openssl.make
> > index 988ff36e6..2ffd9b4b6 100644
> > --- a/rules/openssl.make
> > +++ b/rules/openssl.make
> > @@ -114,6 +114,11 @@ ifdef PTXCONF_OPENSSL_LEGACY
> >  		/usr/lib/ossl-modules/legacy.so)
> >  endif
> >  
> > +ifdef PTXCONF_OPENSSL_CRYPTODEV
> > +	@$(call install_copy, openssl, 0, 0, 0644, -, \
> > +		/usr/lib/engines-3/devcrypto.so)
> > +endif
> > +
> >  	@$(call install_lib, openssl, 0, 0, 0644, libssl)
> >  	@$(call install_lib, openssl, 0, 0, 0644, libcrypto)
> 
> Ladis, could you perhaps comment on this?  I saw you contributed
> cryptodev patches lately with an e-mail address different from the one
> I used to initially Cc you on this series.  Trying the other address now.

I've seen that, I just do not have anything interesting to add, but since
you asked directly, let me put in a few historical notes.

I added cryptodev back then for iMX CAAM when the customer was using
openssl-1.0. Later on another customer wanted to use hw engine with
Octeon MIPS based CPU where cryptographic acceleration is implemented
as another coprocessor (pretty much same as floating point unit is
implemented). That was with openssl-1.1 and Octeon reached end of
production meanwhile.

So now, once it is clear I haven't used openssl-3.5 with cryptodev
I can only add your change looks good and I'm all for including it.

Per https://openssl-library.org/post/2025-04-08-openssl-35-final-release/
3.5 will be supported until April 8, 2030 and given a number of vendor
engines around, upgrading to 4.0 does not sound like a viable option.
Let's wait what 4.1 come with :)

	ladis