Thanks Mike, I don't know really what cause this, but just completed an upgrade of openssl (build) and now is working, so definitely this was caused by this
El dom, 4 jun 2023 a las 23:28, Michael Jumper (<[email protected]>) escribió: > On 6/4/23 11:05, David Rodriguez wrote: > > > > Sorry, forget the one for libssl-dev > > > > ~$ apt list libssl-dev > > > > libssl-dev/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.10 amd64 > > [instalado] > > > > Well, that looks good, however: > > > > > ~$ openssl version > > OpenSSL 1.1.1n 15 Mar 2022 > > > > ~$ apt list openssl > > > > openssl/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.10 amd64 > > [installed] > > openssl/jammy-updates,jammy-security 3.0.2-0ubuntu1.10 i386 > > > > That looks pretty fishy. Something is definitely wrong if OpenSSL 3.0.2 > is installed according to the package manager, but the OpenSSL binary > itself thinks it is version 1.1.1n. > > When I try the same, OpenSSL agrees with the package manager regarding > its version: > > # apt install openssl > ... > Unpacking openssl (3.0.2-0ubuntu1.10) ... > Setting up openssl (3.0.2-0ubuntu1.10) ... > # openssl version > OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022) > # > > I'm not sure why your system is in this state, but it looks like there > are conflicting versions of OpenSSL installed, the build is picking up > the 1.1.1n version (which has the FIPS_mode() function), but then things > are actually being run against 3.0.2 (which doesn't). > > - Mike > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
