Conversation
This updates all sources in deps/openssl/openssl by:
$ git clone git@github.com:quictls/openssl.git
$ cd openssl
$ cd ../node/deps/openssl
$ rm -rf openssl
$ cp -R ../../../openssl openssl
$ rm -rf openssl/.git* openssl/.travis*
$ git add --all openssl
$ git commit openssl
After an OpenSSL source update, all the config files need to be
regenerated and committed by:
$ make -C deps/openssl/config
$ git add deps/openssl/config/archs
$ git add deps/openssl/openssl
$ git commit
|
Review requested:
|
nodejs-github-bot
added
dependencies
github-actions
bot
removed
the
request-ci
|
@RafaelGSS, the differences between archs are cosmetic, and can be easily handled by I used this to compare archs against list=`ls deps/openssl/config/archs`;\
for a in $list; do\
diff -aur deps/openssl/config/archs/linux-x86_64/no-asm/include\
deps/openssl/config/archs/$a/no-asm/include;\
done |
If #42978 lands first, I can recreate this one for master and another one for v17.x then. WDYT? |
SGTM. I suggest when you update/recreate the one for master check if the commits would cherry-pick cleanly to v17.x-staging. If they do then we don't need a v17.x specific PR (we can cherry-pick once the one on master lands), otherwise if there are conflicts we'll need to open a v17.x specific PR. |
|
Closing in favor of: #43022 |
6 participants
Updated OpenSSL dep to OpenSSL-3.0.3+quic using the maintenance guide.
Refs: https://mta.openssl.org/pipermail/openssl-announce/2022-May/000223.html