lukechilds/node - node - Gitea: Git with a cup of tea

9147 Commits

131 Branches

446 Tags

325 MiB

Branch: v0.10-staging

Commit Graph

Author	SHA1	Message	Date
Ben Noordhuis	f8cb0dcf67	crypto,tls: remove SSLv2 support Remove support for SSLv2 because of DROWN (CVE-2016-0800). Use of the `--enable-ssl2` flag is now an error; node will print an error message and exit. Fixes: https://github.com/nodejs/LTS/issues/80 PR-URL: https://github.com/nodejs/node/pull/5529 Reviewed-By: Rod Vagg <rod@vagg.org>	9 years ago
Julien Gilli	8d045a30e9	tests: add TLS tests matrix Add a test that goes through the whole matrix of: - command line options (--enable-ssl*) - secureOptions - secureProtocols and makes sure that compatible test setups actually work as expected. The test works by spawning two processes for each test case: one client and one server. The test passes if a SSL/TLS connection from the client to the server is successful and the test case was supposed to pass, or if the connection couldn't be established and the test case was supposed to fail. The test is currently located in the directory 'test/external' because it has external dependencies.	10 years ago

Author

SHA1

Message

Date

Ben Noordhuis

f8cb0dcf67

crypto,tls: remove SSLv2 support

Remove support for SSLv2 because of DROWN (CVE-2016-0800).

Use of the `--enable-ssl2` flag is now an error; node will print an
error message and exit.

Fixes: https://github.com/nodejs/LTS/issues/80
PR-URL: https://github.com/nodejs/node/pull/5529
Reviewed-By: Rod Vagg <rod@vagg.org>

9 years ago

Julien Gilli

8d045a30e9

tests: add TLS tests matrix

Add a test that goes through the whole matrix of:
- command line options (--enable-ssl*)
- secureOptions
- secureProtocols

and makes sure that compatible test setups actually work as expected.

The test works by spawning two processes for each test case: one client
and one server. The test passes if a SSL/TLS connection from the client
to the server is successful and the test case was supposed to pass, or
if the connection couldn't be established and the test case was supposed
to fail.

The test is currently located in the directory 'test/external' because
it has external dependencies.

10 years ago

2 Commits (v0.10-staging)