node/benchmark/tls
Adam Majer 9cde7a033e
crypto: don't disable TLS 1.3 without suites
In the manual page, there is a statement that ciphersuites contain
explicit default settings - all TLS 1.3 ciphersuites enabled.
In node, we assume that an empty setting mean no ciphersuites and
we disable TLS 1.3. A correct approach to disabling TLS 1.3 is to
disable TLS 1.3 and by not override the default ciphersuits
with an empty string.

So, only override OpenSSL's TLS 1.3 ciphersuites with an explicit
list of ciphers. If none are acceptable, the correct approach is
to disable TLS 1.3 instead elsewhere.

Fixes: https://github.com/nodejs/node/issues/43419

PR-URL: https://github.com/nodejs/node/pull/43427
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Paolo Insogna <paolo@cowtech.it>
Reviewed-By: James M Snell <jasnell@gmail.com>
2022-06-27 09:47:13 +01:00
..
convertprotocols.js benchmark: use let instead of var in tls 2020-03-30 10:16:18 +02:00
secure-pair.js crypto: don't disable TLS 1.3 without suites 2022-06-27 09:47:13 +01:00
throughput-c2s.js crypto: don't disable TLS 1.3 without suites 2022-06-27 09:47:13 +01:00
throughput-s2c.js crypto: don't disable TLS 1.3 without suites 2022-06-27 09:47:13 +01:00
tls-connect.js crypto: don't disable TLS 1.3 without suites 2022-06-27 09:47:13 +01:00