Hi, 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 ? Jérémy
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. Sebastian
Le jeu. 26 mai 2022 à 09:57, Sebastian Andrzej Siewior < sebastian@breakpoint.cc> a écrit : 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
np. me, too. If there is anything you want me to look at, just yell. For now I consider this handled. Sebastian
We believe that the bug you reported is fixed in the latest version of
nodejs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1011339@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jérémy Lal <kapouer@melix.org> (supplier of updated nodejs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Fri, 27 May 2022 15:48:16 +0200
Source: nodejs
Architecture: source
Version: 16.15.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers <pkg-javascript-devel@alioth-lists.debian.net>
Changed-By: Jérémy Lal <kapouer@melix.org>
Closes: 977792 1011100 1011339
Changes:
nodejs (16.15.0+dfsg-1) unstable; urgency=medium
.
* New upstream version 16.15.0+dfsg
* Go back to +dfsg
* dfsg-exclude undici (missing source for compiled wasm)
* Will B-D undici <!pkg.nodejs.nobuiltin> when available
* bash-completion from node --completion-bash (Closes: #977792)
* Patches:
+ build/skip-crypto-engine-check no longer needed
+ test-diagnostic-dir-cpu-prof is flaky on riscv64
(Closes: #1011100)
* Update README.source
* Fix undici source name
* Update openssl.cnf to fix tests on mipsel (Closes: #1011339)
* Improve doc-generator
Checksums-Sha1:
6cd958b503c130b49f69191e9c80b5ec348dc983 3853 nodejs_16.15.0+dfsg-1.dsc
0aa32481f8da93b1873708a0b6ccd98c7e9ee826 235472 nodejs_16.15.0+dfsg.orig-types-node.tar.xz
b8858275579422d893ee3d2d2db009b8e3bafd52 21817552 nodejs_16.15.0+dfsg.orig.tar.xz
b14ee715bdc6d4410b384dafd8b02a3cc77d9f04 159232 nodejs_16.15.0+dfsg-1.debian.tar.xz
8a925529ceefa12ec6d2725c0d30de78f40c7ca5 10205 nodejs_16.15.0+dfsg-1_source.buildinfo
Checksums-Sha256:
2f8573b0e8be14caa3d4513e9da0edc568cfb58324b72e8e93b31cea56f3d193 3853 nodejs_16.15.0+dfsg-1.dsc
3079b87b3a151438b1cc2b6410e0402f691d8f66f54cf9cb80598e3bef9b8915 235472 nodejs_16.15.0+dfsg.orig-types-node.tar.xz
37d50c9358998ad3aef3b80b31b7644fd7e1ce6dc0ebaaea679497df1c28c18b 21817552 nodejs_16.15.0+dfsg.orig.tar.xz
2177aaf86af54a1e09310a55ef6ab90d6f92b5695f55b3e36607a525db550313 159232 nodejs_16.15.0+dfsg-1.debian.tar.xz
2c9c703653366ea0bf44142dec9dffd73e96a2777a14d362a8636fc54b0b6e48 10205 nodejs_16.15.0+dfsg-1_source.buildinfo
Files:
4bcfdc0b7f601056a0348f30559831bc 3853 javascript optional nodejs_16.15.0+dfsg-1.dsc
1aa4e6286cddae4bbb4d0004f5b818cd 235472 javascript optional nodejs_16.15.0+dfsg.orig-types-node.tar.xz
8eb7216f7c2cdf9c4c4600a145164212 21817552 javascript optional nodejs_16.15.0+dfsg.orig.tar.xz
bfa7822c6e314d651f73bb2dfd634766 159232 javascript optional nodejs_16.15.0+dfsg-1.debian.tar.xz
305879d02f3cf0007fd651cc4731a28a 10205 javascript optional nodejs_16.15.0+dfsg-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmKQ2OcSHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN0H00P+wZ7PGO4EIvWcKiuEuEBpcJVPm9AtvK2
oYx6UjuUqmKUm86t3AHE2RU1/BfklXivbv3KHFwp561ECfFtse6MS4XEHqpQtuDG
utxqJHDpbGrr5NkD8tHJV8rpo+2khggkCBRP5sDECIJKqbPGD9MIAKlFWJVqhZ0j
ZuWN083/NkgNZNPVqPjcEDqo54x/0FDO/dInBSknJPvZ8kgLLsDHDG/3tm4NUBeR
xD06jaOYB+Et5TKKzuGIeUvtErM/5hLaTjqY5PMjDjkFl4kHV4MYJC8atLL3JXfX
iRP/cL7/R3yVeXD3jXrTXcuzndn9tjGuxyYR9JtOMIY4vGwzG54gB/nBY+xJ925+
PpED1/0FG/2Zgzl3ZviyuzT3PF8VuAh3QOtrIxzEYKyxce+z5zVKq7c+VcP0gIZ9
OJBSLeJxSJUSNq2VY6BwYFMH6zw62Vk7mrj5HLwiJuycoPnPQFJCbREMdSTqlLsJ
x4CI/jq9kwUL1tGNRFfdm/2JGTMAj/8Tg2r5GMwBr3H48UCuSb89TbuYBWSHrCWf
+RuBwRbZAq04xwhBtbMgLvHo0SapTvCJgkj+ujynMov/KV9F+ROQ5F+lMv5J93VO
zrks0++iG4fBhnxhkP74m/wd9hu45uLMd+ULjvgyDmBrPgxsLaLzCGE2XyHhmRTC
ajJsi+Z7GrLT
=cjOS
-----END PGP SIGNATURE-----
Le ven. 27 mai 2022 à 16:54, Debian Bug Tracking System < owner@bugs.debian.org> a écrit : That didn't fix the issue we're seeing. I tried nodejs in a qemu mips, but couldn't reproduce, so will try on a porter box.
Le jeu. 26 mai 2022 à 19:23, Sebastian Andrzej Siewior < sebastian@breakpoint.cc> a écrit : This succeeds: ./node test/parallel/test-crypto-key-objects.js This fails only on mipsel (tested on eller porterbox) OPENSSL_CONF=/etc/ssl/openssl.cnf ./node test/parallel/test-crypto-key-objects.js I suppose the problem comes from openssl: - nodejs code calling OPENSSL_init_ssl doesn't depend on mips - nodejs runs on other "slow" architectures, if it was a race condition we would see it there sometimes. Jérémy
Hi Sebastian, Le dim. 29 mai 2022 à 16:27, Jérémy Lal <kapouer@melix.org> a écrit : Any hint or idea about this ? Even wild ideas that I could try, before I have to remove the files from mips. Jérémy
Hi Jérémy, for some reason ossl_err_load_crypto_strings() is not invoked on mipsel but is invoked on amd64. Therefore the string is missing on mipsel because this function actually loads all the strings during lib init. Digging further, on amd64 is invoked once with OPENSSL_init_crypto(OPENSSL_INIT_LOAD_CONFIG) and a second time with OPENSSL_init_crypto(OPENSSL_INIT_LOAD_CRYPTO_STRINGS) so all the strings are loaded. On mipsel however I see OPENSSL_init_crypto(OPENSSL_INIT_LOAD_CONFIG) OPENSSL_init_crypto(OPENSSL_INIT_ADD_ALL_CIPHERS | OPENSSL_INIT_ADD_ALL_DIGESTS) Now I need to take a nap before I can continue digging but this is my progress so far. Sebastian
Hi,
on amd64 the entry point to init is:
| #0 OPENSSL_init_crypto (opts=opts@entry=64, settings=settings@entry=0x0) at ../crypto/init.c:563
| #1 0x00007fbb6ede32b7 in ossl_engine_table_select (table=table@entry=0x7fbb6f0806c0 <rand_table>, nid=nid@entry=1,
| f=f@entry=0x7fbb6ef6e985 "../crypto/engine/tb_rand.c", l=l@entry=62) at ../crypto/engine/eng_table.c:206
| #2 0x00007fbb6ede490d in ENGINE_get_default_RAND () at ../crypto/engine/tb_rand.c:61
| #3 0x00007fbb6ee6a8f0 in RAND_get_rand_method () at ../crypto/rand/rand_lib.c:208
| #4 0x00007fbb6ee6afb6 in RAND_status () at ../crypto/rand/rand_lib.c:311
| #5 0x00007fbb6ffdd310 in node::crypto::CheckEntropy () at ../src/crypto/crypto_util.cc:66
| #6 0x00007fbb6ffdd342 in node::crypto::EntropySource (buffer=0x7ffcc47a8ef0 "", length=8) at ../src/crypto/crypto_util.cc:79
| #7 0x00007fbb70a11f56 in v8::base::RandomNumberGenerator::RandomNumberGenerator (
| this=0x7fbb71e75740 <v8::base::(anonymous namespace)::GetPlatformRandomNumberGenerator()::object>) at ../deps/v8/src/base/utils/random-number-generator.cc:41
| #8 0x00007fbb70a12ebe in v8::base::LeakyObject<v8::base::RandomNumberGenerator>::LeakyObject<>() (
| this=0x7fbb71e75740 <v8::base::(anonymous namespace)::GetPlatformRandomNumberGenerator()::object>) at /usr/include/c++/11/new:175
| #9 v8::base::(anonymous namespace)::GetPlatformRandomNumberGenerator () at ../deps/v8/src/base/platform/platform-posix.cc:100
| #10 v8::base::(anonymous namespace)::GetPlatformRandomNumberGenerator () at ../deps/v8/src/base/platform/platform-posix.cc:100
| #11 v8::base::OS::GetRandomMmapAddr () at ../deps/v8/src/base/platform/platform-posix.cc:289
| #12 0x00007fbb7035c1b6 in v8::internal::Heap::SetUp (this=this@entry=0x555611f6c540) at ../deps/v8/src/heap/heap.cc:5523
| #13 0x00007fbb702e8539 in v8::internal::Isolate::Init (this=this@entry=0x555611f62240, startup_snapshot_data=startup_snapshot_data@entry=0x7ffcc47a92b0,
| read_only_snapshot_data=read_only_snapshot_data@entry=0x7ffcc47a92d0, can_rehash=<optimized out>) at ../deps/v8/src/execution/isolate.cc:3650
| #14 0x00007fbb702e9158 in v8::internal::Isolate::InitWithSnapshot (this=this@entry=0x555611f62240, startup_snapshot_data=startup_snapshot_data@entry=0x7ffcc47a92b0,
| read_only_snapshot_data=read_only_snapshot_data@entry=0x7ffcc47a92d0, can_rehash=<optimized out>) at ../deps/v8/src/execution/isolate.cc:3519
| #15 0x00007fbb706fb8be in v8::internal::Snapshot::Initialize (isolate=0x555611f62240) at ../deps/v8/src/snapshot/snapshot.cc:168
| #16 v8::internal::Snapshot::Initialize (isolate=isolate@entry=0x555611f62240) at ../deps/v8/src/snapshot/snapshot.cc:149
| #17 0x00007fbb701cb756 in v8::Isolate::Initialize (isolate=0x555611f62240, params=...) at ../deps/v8/src/api/api.cc:8665
| #18 0x00007fbb6fe99b45 in node::NodeMainInstance::NodeMainInstance (this=this@entry=0x7ffcc47a9490, params=params@entry=0x7ffcc47a94f0, event_loop=0x7fbb6f2ae260,
| platform=platform@entry=0x555611f5ce70, args=..., exec_args=std::vector of length 2, capacity 2 = {...}, per_isolate_data_indexes=0x0)
| at ../src/node_main_instance.cc:94
| #19 0x00007fbb6fe101eb in node::Start (argc=<optimized out>, argv=<optimized out>) at ../src/node.cc:1168
| #20 0x00007fbb6f2ef7fd in __libc_start_main (main=0x5556110ba000 <main(int, char**)>, argc=3, argv=0x7ffcc47a96b8, init=<optimized out>, fini=<optimized out>,
| rtld_fini=<optimized out>, stack_end=0x7ffcc47a96a8) at ../csu/libc-start.c:332
| #21 0x00005556110ba0da in _start ()
basivally, Heap::SetUp() -> node::crypto::EntropySource() -> RAND_status()
and this does the init including loading strings.
On mipsel and assuming the backtrace works:
| #0 OPENSSL_init_crypto (opts=<optimized out>, settings=0x55645ac0) at ../crypto/init.c:563
| #1 0x75d61f9c in std::_Rb_tree_node<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >::_M_valptr () at ../src/node.cc:1083
| #2 0x75d62660 in std::allocator<std::__detail::_Hash_node_base*>::~allocator () at ../src/node.cc:975
| #3 0x75d626bc in std::__get_helper<0u, node::NodeTraceStateObserver*, std::default_delete<node::NodeTraceStateObserver> > () at ../src/node.cc:1142
| #4 0x7545b540 in __libc_start_main () from /lib/mipsel-linux-gnu/libc.so.6
| #5 0x5557fb74 in __start ()
So it appears we get there earlier and from libstd++. It could be that the
backtrace is just nuts. Now I am a little curious why strings are not loaded
eventually…
Sebastian
Hi, I added RAND_status() as the first instruction in Start() (src/node.cc) before InitializeOncePerProcess(). With this change the testsuite passes on eller. So having the same init chain as on amd64 works. Now let me figure out why the other init chain does not work… Sebastian
control: forwarded -1 https://github.com/openssl/openssl/issues/18535 Hi, Okay. So if you do OPENSSL_init_crypto(OPENSSL_INIT_LOAD_CONFIG OPENSSL_INIT_LOAD_CRYPTO_STRINGS | OPENSSL_INIT_ADD_ALL_CIPHERS | OPENSSL_INIT_ADD_ALL_DIGESTS, settings); in src/node.cc instead just OPENSSL_INIT_LOAD_CONFIG as it is currently done, then it will pass. The difference on mipsel is the call chain. Due to openssl internal locking it can't load strings. As of now I think that this is a bug in openssl and I forwarded it to upstream. So you have a workaround you may try if you want something asap and I let you know what upstream thinks about this ;) Sebastian
We believe that the bug you reported is fixed in the latest version of
nodejs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1011101@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jérémy Lal <kapouer@melix.org> (supplier of updated nodejs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Mon, 13 Jun 2022 09:11:34 +0200
Source: nodejs
Architecture: source
Version: 16.15.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers <pkg-javascript-devel@alioth-lists.debian.net>
Changed-By: Jérémy Lal <kapouer@melix.org>
Closes: 977792 1011101 1012670
Changes:
nodejs (16.15.1+dfsg-1) unstable; urgency=medium
.
* New upstream version 16.15.1+dfsg
* Fix completion generation, support "nodejs" cli
Closes: #977792
* Patch to fix mipsel crypto init error strings (Closes: #1011101)
* Patch: more flaky riscv64 cpu tests (Closes: #1012670)
Checksums-Sha1:
437c11ddd61c1a3346e0f3d595784969ed1c32bd 3853 nodejs_16.15.1+dfsg-1.dsc
1771bd68477dd1af1ad944ce71406788463cbdc1 235544 nodejs_16.15.1+dfsg.orig-types-node.tar.xz
cdbfbb786d45a6b717a84557b6a9c0026324dd72 21856440 nodejs_16.15.1+dfsg.orig.tar.xz
23485ff790d342c0ae20fa95e2001ee6be50edd4 159552 nodejs_16.15.1+dfsg-1.debian.tar.xz
3f5b948bc9677c3b605e48e40798b98c79e6446e 10176 nodejs_16.15.1+dfsg-1_source.buildinfo
Checksums-Sha256:
e0aecef155ac99242ac66b5c9e2f422f9b66b8ab103b3ceee4bff87240d47885 3853 nodejs_16.15.1+dfsg-1.dsc
1c1382942f9ca5e7fb4ec2c837a183d37674d023ab93da024808d254ac6c7f87 235544 nodejs_16.15.1+dfsg.orig-types-node.tar.xz
348d462dbae6e9f5e71bae770df3b1748852d202ea73586b1b83ad9a4de5dfa7 21856440 nodejs_16.15.1+dfsg.orig.tar.xz
4871b087b623c11cbb41c95bb5ac113b05bb9285f9f5e6bd6f5a13d0b08dd11e 159552 nodejs_16.15.1+dfsg-1.debian.tar.xz
619958c1f1df7e1c5eb5ac004a4c08b4515f26b5c030f7a629bc521e0f428be8 10176 nodejs_16.15.1+dfsg-1_source.buildinfo
Files:
70aeb3310bc8e243c31f535c99fc03dc 3853 javascript optional nodejs_16.15.1+dfsg-1.dsc
f73ec0db4b00230ead76a997122a2400 235544 javascript optional nodejs_16.15.1+dfsg.orig-types-node.tar.xz
cc24ab522a5f78edb3181ea3412abe78 21856440 javascript optional nodejs_16.15.1+dfsg.orig.tar.xz
0c7acb654de6a725e286e94b3b6c3b65 159552 javascript optional nodejs_16.15.1+dfsg-1.debian.tar.xz
4cc72b9222f081f05cc603297bf44cf2 10176 javascript optional nodejs_16.15.1+dfsg-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmKm64ASHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN0IW0P/ijLtHF8FWWvYcWnbtptqe/jWvPszj4S
a6Dk5hAzGuTCDLF0buiC9QANsZIP6mIdKal1+s4KYmLLk0tcc70sHRMqoL8d9M7X
WGjb5eJwLewBWUaGKeGSdrrYXrLFiTQihfq+WOQ3ssRW0fPBcm9yYyJjJQjC41Ej
Wi6uVu6oVU5Ki+52bD3SPSBYeekhtyOg+BMkHnVsyQTh7uk8azpdB5sIMznLh9cM
Bpjq9HG6R7XrQbbHlR8xfua8XO2c+qcTK04bK1YAXrHaAM7S6tU69R7rLcdSKouR
C5HcnAxOw8Gf0dYB+LNMitvzKOW8zcmM4JAN25eAQ/92nZauDGDb1z340X5S6cNX
tWYLcDd9QPb/Ezg94dzu2TyvfpfW4lx+xJMgZ22RN5ssQxsmvOqF2Aj5f0J87kSI
1XvHyihsz8X7ZjBn71yQscUwhOC8yMoG5sYtnwpP2mTeDNe2AXECAs/5VrHOboju
Gaammv1IYb1yG4xGgugdL8bE6qb3y7IZdcmvrcISm8vPkpZz6iPKFC25A/o2T4So
YC7QsbWw6lY892vnR5AVlK5D9xxBjoTm6pXGSkh+7f0GVJ1vD/AuS/YiSFBIVIBW
6r+6ukHmOomDan0DGGrE4E1JiFS9WKMJSGgAf1OQW6xQyKawUcJ6JViwB2wpvtH9
6r1wpzDnoq0W
=Pp9+
-----END PGP SIGNATURE-----
We believe that the bug you reported is fixed in the latest version of openssl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1011339@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Andrzej Siewior <sebastian@breakpoint.cc> (supplier of updated openssl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) Format: 1.8 Date: Mon, 13 Jun 2022 22:16:39 +0200 Source: openssl Architecture: source Version: 3.0.3-8 Distribution: unstable Urgency: medium Maintainer: Debian OpenSSL Team <pkg-openssl-devel@alioth-lists.debian.net> Changed-By: Sebastian Andrzej Siewior <sebastian@breakpoint.cc> Closes: 1011339 Changes: openssl (3.0.3-8) unstable; urgency=medium . * Update to openssl-3.0 head. * Avoid reusing the init_lock for a different purpose (Closes: #1011339). Checksums-Sha1: 4abad0e1d8572a290c87833f905a89ecc3bf177b 2637 openssl_3.0.3-8.dsc c0e33bd4ebdff1f310dd16eebc89b9e63fdb6efa 157400 openssl_3.0.3-8.debian.tar.xz Checksums-Sha256: 093ee645846839847ef0751c422f81847a1fb22fbe3cc9ea2f5ca00f924017e8 2637 openssl_3.0.3-8.dsc 23334b0edc0adeab429a4bbddfeba3a66db194231b01eaa5923d4048fb3c49c0 157400 openssl_3.0.3-8.debian.tar.xz Files: d1a2a6c34f150314769e56ff8ae70470 2637 utils optional openssl_3.0.3-8.dsc f2226129b5a23d65869ba1ba500de190 157400 utils optional openssl_3.0.3-8.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQJMBAEBCgA2FiEEZCVGlf/wqkRmzBnme5boFiqM9dEFAmKnpucYHHNlYmFzdGlh bkBicmVha3BvaW50LmNjAAoJEHuW6BYqjPXRDE0QAJqI8TYVYN5dcMbvhHkK6ygd mSE1agfh7yewS7FU5e4nw6uR9sD+TCtGesF4TBImSI642mcIytjhOCcuus+mODAq NvTtxYy2d05i/0gsQjRb2EAttsWTM74tgiyriIYaARR0uWmDtkAhaQ2vqmIcVRLE X8b0mq4ebGgo6xcAw/2Jg7+WEqvosqKFOfQf1MABu4sbNC6X3q4e/SXQyVMivw/o Ey1AO0BmHO+lxlcyLdMvf9ett4JnxTdDn72q3ZGJJXbkFW0onVuW1b+ZKq8fDyq4 hFmjR9nCB5xKfXozURtKjdOXra46ownnAR7g8LAJnrY7g7wPnCuqhTIT66F8T834 mQdJgC4W4lp8/O5aNNwPojfuO/ZriP38GzONbxkeQFqMveMaghNIbeabhB1lnecl aLtqG4DTI0jAWKOyMIbfu8XtpgubrPalCLNikhtHIuRdztLa2JqqfEunShqD5IKL lv/nHiV5Y1islsjyA+Xzn61c9TrQFLwkZmGk6yIwG1kjzLXa8bKA/kfSGwFYMNa+ jobDw57GvhkdfYP7emd4nsiLw2sqcXaXB5wB5kabIxzZEXrDKd9iV5WtyJm270HX +72NuCV/yoc44aEZCdwHsyg79EZcmEYR8916EgYZdSmyjMHHy+p9uEPJYgz4myDl QwJ7hsGrQwZ/U+NpmkxS =QG5V -----END PGP SIGNATURE-----
Hi, I confirmed on eller that nodejs 16.15.0+dfsg-1 builds with openssl 3.0.3-7. I was about to give-it-back but then noticed that you uploaded a new version with the workaround I mentioned. You may drop the workaround in your future upload ;) Sebastian
Le mar. 14 juin 2022 à 23:05, Sebastian Andrzej Siewior < sebastian@breakpoint.cc> a écrit : Yes, I saw that in the latest openssl upload. Thank you. Jérémy