[v10.x] Update openssl 1.1.1i#36541
Conversation
nodejs-github-bot
added
openssl
github-actions
bot
removed
the
request-ci
|
@richardlau thanks for that. Should we add some documentation in https://github.com/nodejs/node/blob/master/doc/guides/maintaining-openssl.md to explain what you need to do in order to get updates across all of the active version? |
I just followed those instructions from step 2 onwards but for the |
|
@richardlau that's what I figured, but since it came as a surprise to people, I was thinking having it documented would better explain the work we need to do in order to support releases across all of the release lines. I'll put together a PR. |
Refs: nodejs#36541 Expand the instructions to cover what is needed when updates are required across all active release lines
|
PR #36554 to add instructions |
richardlau
added
commit-queue
This updates all sources in deps/openssl/openssl by:
$ cd deps/openssl/
$ rm -rf openssl
$ tar zxf ~/tmp/openssl-1.1.1i.tar.gz
$ mv openssl-1.1.1i openssl
$ git add --all openssl
$ git commit openssl
PR-URL: nodejs#36541
Reviewed-By: Michael Dawson <midawson@redhat.com>
After an OpenSSL source update, all the config files need to be
regenerated and comitted by:
$ cd deps/openssl/config
$ make
$ git add deps/openssl/config/archs
$ git add deps/openssl/openssl/include/crypto/bn_conf.h
$ git add deps/openssl/openssl/include/crypto/dso_conf.h
$ git add deps/openssl/openssl/include/openssl/opensslconf.h
$ git commit
PR-URL: nodejs#36541
Reviewed-By: Michael Dawson <midawson@redhat.com>
richardlau
force-pushed
the
openssl-v10.x
branch
from
ed69000 to
b0608b5
Compare
|
Landed in bd44b0e...b0608b5. |
4 participants
The first commit (
deps: upgrade openssl sources to 1.1.1i) is cherry-picked from #36521.The second commit is the regenerated OpenSSL configuration files as the equivalent commit does not cherry pick cleanly (see #32971 (comment) for some history).
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes