Perfect your code
With built-in code review tools, GitHub makes it easy to raise the quality bar before you ship. Join the 36 million developers who've merged over 200 million pull requests.
Sign up for free See pricing for teams and enterprisesUpdate openssl 1.1.1c #28211
Conversation
sam-github
added some commits
Jun 12, 2019
This comment has been minimized.
This comment has been minimized.
nodejs-github-bot
commented
Jun 13, 2019
•
|
Sadly, an error occurred when I tried to trigger a build. :( |
nodejs-github-bot
added
the
openssl
label
Jun 13, 2019
sam-github
force-pushed the
sam-github:update-openssl-1.1.1c
branch
from
2a10271
to
66b4930
Jun 13, 2019
sam-github
added
the
backport-requested-v10.x
label
Jun 13, 2019
This comment has been minimized.
This comment has been minimized.
|
backport: #28212 |
This comment has been minimized.
This comment has been minimized.
|
@nodejs/releasers @nodejs/lts This cherry-picks clean onto 12.x-staging, but it does not onto v10.x-staging, so I backported. Possibly it needs to "bake" by being in a 12.x release before getting released on 10.x. |
sam-github
added
the
baking-for-lts
label
Jun 13, 2019
This comment has been minimized.
This comment has been minimized.
We did reserve a date (June 25th) for a security release across all currently supported versions of Node.js. This OpenSSL update seems like the sort of thing the reserved date was intended for (non-critical security updates). |
sam-github
referenced this pull request
Jun 13, 2019
Closed
Bot does not post or edit comment on new Jenkins builds #239
jasnell
approved these changes
Jun 14, 2019
ryzokuken
approved these changes
Jun 14, 2019
|
RSLGTM. I think you'd need to run |
shigeki
approved these changes
Jun 14, 2019
This comment has been minimized.
This comment has been minimized.
|
@ryzokuken I've never run license-builder.sh, and its not part of the OpenSSL update instructions (see deps/openssl/config/README.md). Should it be? OpenSSL doesn't change its license in patches, but when I tried running it, I noticed the valgrind license seems out of date. |
tniessen
approved these changes
Jun 16, 2019
|
RSLGTM, thanks Sam. |
danbev
added
the
author ready
label
Jun 17, 2019
BridgeAR
added a commit
to BridgeAR/node
that referenced
this pull request
Jun 17, 2019
BridgeAR
added a commit
to BridgeAR/node
that referenced
this pull request
Jun 17, 2019
BridgeAR
added a commit
to BridgeAR/node
that referenced
this pull request
Jun 17, 2019
This comment has been minimized.
This comment has been minimized.
|
Landed in b6326ce...7cb8981 |
BridgeAR
closed this
Jun 17, 2019
BridgeAR
added a commit
that referenced
this pull request
Jun 17, 2019
BridgeAR
added a commit
that referenced
this pull request
Jun 17, 2019
BridgeAR
added a commit
that referenced
this pull request
Jun 17, 2019
targos
added a commit
that referenced
this pull request
Jun 18, 2019
targos
added a commit
that referenced
this pull request
Jun 18, 2019
targos
added a commit
that referenced
this pull request
Jun 18, 2019
This comment has been minimized.
This comment has been minimized.
|
Looks like this update causes |
This comment has been minimized.
This comment has been minimized.
|
The test still passes given enough time but performance of getDiffieHellman() is much much worse than before. Might be not-a-bug if it’s due to a security fix or something? |
This comment has been minimized.
This comment has been minimized.
|
Pummel test issues workarounds/fixes in #28390 |
sam-github
deleted the
sam-github:update-openssl-1.1.1c
branch
Jun 24, 2019
This comment has been minimized.
This comment has been minimized.
|
@Trott re:
I wouldn't expect bisect to work across any openssl updates, because upstream sources are updated in a seperate commit from the config files generated by node's build system, according to our openssl update process, see https://github.com/nodejs/node/blob/master/deps/openssl/config/README.md#4-commit-and-make-test. There are some pros and cons to changing the process we use to vendor in openssl updates. In general, every commit would pass |
This comment has been minimized.
This comment has been minimized.
|
@sam-github Ah, thanks for the explanation. That makes a lot of sense. |
sam-github commentedJun 13, 2019
See:
Note openssl 1.1.1c fixes CVE https://www.openssl.org/news/vulnerabilities.html#2019-1543, but I believe this does not affect node since #26537 protects it. Arguably, we could back out #26537, except that it can creep back in if an external OpenSSL 1.1.1a or b is used. Best to leave, I think.
/to @nodejs/crypto
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes