Le jeu. 26 mai 2022 à 09:01, Sebastian Andrzej Siewior < sebast...@breakpoint.cc> a écrit :
> On 2022-05-16 22:38:44 [+0200], Jérémy Lal wrote: > > Last time so many openssl-related test failures happened, > > OPENSSL_CONF env was set to a relative path, and nodejs/openssl3 > > expected an absolute path. > > I don't understand why mipsel is different here. The init looks okay. I > copied the .cnf from 3.0 > cp /etc/ssl/openssl.cnf deps/openssl/openssl/apps/openssl.cnf > > and then removed the protocol/ sec-level override: > > --- /etc/ssl/openssl.cnf 2022-05-13 21:25:01.000000000 +0000 > +++ deps/openssl/openssl/apps/openssl.cnf 2022-05-25 > 20:58:47.602964293 +0000 > @@ -52,7 +52,6 @@ > > [openssl_init] > providers = provider_sect > -ssl_conf = ssl_sect > > # List of providers to load > [provider_sect] > @@ -389,10 +388,3 @@ > # Certificate revocation > cmd = rr > oldcert = $insta::certout # insta.cert.pem > - > -[ssl_sect] > -system_default = system_default_sect > - > -[system_default_sect] > -MinProtocol = TLSv1.2 > -CipherString = DEFAULT:@SECLEVEL=2 > > with this change the suite passed on mipsel. You could move that file to > debian/ for the testsuite and I keep thinking about not touching that > file at all. > I could keep investigating why mipsel is different here but I'm short on > time right now and eller isn't exactly a fast beast. > Side note: I built it with -j3 and I hope that the build time reduced > compared to the initial -j1 (I had to build a few times because -nc > didn't skip anything…). > Shout out... I've tried some things but it still fails. I think there's some bug or option activated on mipsel, that prevents openssl from loading error strings. There are builds on eller.debian.org/~kapouer that you can play with. Help is welcome ! Jérémy > > Sebastian >
