-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to openssl-1.0.2i v4.x #8719
Conversation
This replaces all sources of openssl-1.0.2i.tar.gz into deps/openssl/openssl PR-URL: nodejs#8714 Reviewed-By: Fedor Indutny <[email protected]>
All symlink files in `deps/openssl/openssl/include/openssl/` are removed and replaced with real header files to avoid issues on Windows. Two files of opensslconf.h in crypto and include dir are replaced to refer config/opensslconf.h. PR-URL: nodejs#8714 Reviewed-By: Fedor Indutny <[email protected]>
`x86masm.pl` was mistakenly using .486 instruction set, why `cpuid` (and perhaps others) are requiring .686 . Fixes: nodejs#589 PR-URL: nodejs#1389 Reviewed-By: Fedor Indutny <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Shigeki Ohtsu <[email protected]>
See https://mta.openssl.org/pipermail/openssl-dev/2015-February/000651.html iojs needs to stop using masm and move to nasm or yasm on Win32. Fixes: nodejs#589 PR-URL: nodejs#1389 Reviewed-By: Fedor Indutny <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
Reapply b910613 . Fixes: nodejs#589 PR-URL: nodejs#1389 Reviewed-By: Fedor Indutny <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
In openssl s_client on Windows, RAND_screen() is invoked to initialize random state but it takes several seconds in each connection. This added -no_rand_screen to openssl s_client on Windows to skip RAND_screen() and gets a better performance in the unit test of test-tls-server-verify. Do not enable this except to use in the unit test. Fixes: nodejs#1461 PR-URL: nodejs#1836 Reviewed-By: Ben Noordhuis <[email protected]>
Regenerate asm files with Makefile and CC=gcc and ASM=gcc where gcc-5.4.0. Also asm files in asm_obsolete dir to support old compiler and assembler are regenerated without CC and ASM envs. PR-URL: nodejs#8714 Reviewed-By: Fedor Indutny <[email protected]>
openssl command does not allow to both "-ssl3" and "-no_tls1". A protocol connecting to the server is only specified. PR-URL: nodejs#8714 Reviewed-By: Fedor Indutny <[email protected]>
LGTM if CI is ok. |
@mhdawson can you look into the failures on AIX? https://ci.nodejs.org/job/node-test-commit-aix/1022/nodes=aix61-ppc64/ edit: 2 of the three tests look infra related... re running tests on AIX to be safe https://ci.nodejs.org/job/node-test-commit-aix/1025/ edit 2: failed again running ci against v4.x to see if failures exist on entire release line edit 3: these are known flaky's merging |
/cc @nodejs/build @nodejs/bots it looks like the failed tests were not updated here. Might be worth taking a look into |
AIX failures are marked as flaky and so are expected: These are the ones I saw: not ok 510 parallel/test-https-connect-address-family I believe the connect-address-family ones are flaky on other platforms as well (something to do with IPV6 configuration I think) |
Checklist
make -j4 test
(UNIX), orvcbuild test nosign
(Windows) passesAffected core subsystem(s)
crypto, tls and https
Description of change
Ref: #8714
ci: https://ci.nodejs.org/job/node-test-pull-request/4214/
CC: @indutny or @bnoordhuis or @shigeki