[Pkg-openssl-devel] Bug#1011339: Bug#1011339: openssl: missing errors strings on mipsel

[Jérémy Lal]

Le jeu. 26 mai 2022 à 09:57, Sebastian Andrzej Siewior <
sebastian at breakpoint.cc> a écrit :

> On 2022-05-20 13:07:55 [+0200], Jérémy Lal wrote:
> > nodejs dynamically links to openssl, and since openssl >= 3,
> > on mipsel, some of its tests are failing, see
> > https://buildd.debian.org/status/package.php?p=nodejs
> >
> > The failures look like openssl was configured with no-err, e.g:
> >     AssertionError [ERR_ASSERTION]: Expected values to be strictly
> deep-equal:
> >     + actual - expected
> >
> >       Comparison {
> >     +   message: 'error:1C8000A5:Provider routines::reason(165)'
> >     -   message: 'error:1C8000A5:Provider routines::illegal or
> unsupported padding mode'
> >       }
> >         at Object.<anonymous>
> (/root/debian/nodejs-16.14.2+dfsg/test/parallel/test-crypto-sign-verify.js:59:10)
> >
> > I did not find if nodejs was doing a specific configuration for mipsel.
> >
> > Note that mips64el and other supported archs have no such test failures.
> >
> > Could it be that openssl 3 disables error strings on 32-bits platforms ?
>
> This seems to be unique to mipsel. As I said in #1011101 it works if you
> use openssl.cnf provided by the openssl package and remove the protocol
> override in there.
> What I don't understand why mipsel is different here and currently I
> don't have the time to investigate.
>

Thanks for the feedback.

Indeed, the latest nodejs version (18.x) embeds an updated openssl.cnf,
which is exactly the one
of the openssl debian package, without the [ssl_sect] part at the end.

Why this fails only on mipsel is a mystery to me, maybe some race condition
when initializing openssl,
but this is not a bug.

Jérémy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-openssl-devel/attachments/20220526/03bada3a/attachment.htm>