summaryrefslogtreecommitdiff
path: root/src/node_options.h
diff options
context:
space:
mode:
authorSam Roberts <vieuxtech@gmail.com>2018-11-28 17:58:08 -0800
committerSam Roberts <vieuxtech@gmail.com>2019-03-20 07:48:25 -0700
commit42dbaed4605f44c393a057aad75a31cac1d0e5f5 (patch)
tree096554b95dfb14cef568bfe898018d9bb874305c /src/node_options.h
parent4306300b5ea8d8c4ff3daf64c7ed5fd64055ec2f (diff)
downloadandroid-node-v8-42dbaed4605f44c393a057aad75a31cac1d0e5f5.tar.gz
android-node-v8-42dbaed4605f44c393a057aad75a31cac1d0e5f5.tar.bz2
android-node-v8-42dbaed4605f44c393a057aad75a31cac1d0e5f5.zip
tls: support TLSv1.3
This introduces TLS1.3 support and makes it the default max protocol, but also supports CLI/NODE_OPTIONS switches to disable it if necessary. TLS1.3 is a major update to the TLS protocol, with many security enhancements. It should be preferred over TLS1.2 whenever possible. TLS1.3 is different enough that even though the OpenSSL APIs are technically API/ABI compatible, that when TLS1.3 is negotiated, the timing of protocol records and of callbacks broke assumptions hard-coded into the 'tls' module. This change introduces no API incompatibilities when TLS1.2 is negotiated. It is the intention that it be backported to current and LTS release lines with the default maximum TLS protocol reset to 'TLSv1.2'. This will allow users of those lines to explicitly enable TLS1.3 if they want. API incompatibilities between TLS1.2 and TLS1.3 are: - Renegotiation is not supported by TLS1.3 protocol, attempts to call `.renegotiate()` will always fail. - Compiling against a system OpenSSL lower than 1.1.1 is no longer supported (OpenSSL-1.1.0 used to be supported with configure flags). - Variations of `conn.write('data'); conn.destroy()` have undefined behaviour according to the streams API. They may or may not send the 'data', and may or may not cause a ERR_STREAM_DESTROYED error to be emitted. This has always been true, but conditions under which the write suceeds is slightly but observably different when TLS1.3 is negotiated vs when TLS1.2 or below is negotiated. - If TLS1.3 is negotiated, and a server calls `conn.end()` in its 'secureConnection' listener without any data being written, the client will not receive session tickets (no 'session' events will be emitted, and `conn.getSession()` will never return a resumable session). - The return value of `conn.getSession()` API may not return a resumable session if called right after the handshake. The effect will be that clients using the legacy `getSession()` API will resume sessions if TLS1.2 is negotiated, but will do full handshakes if TLS1.3 is negotiated. See https://github.com/nodejs/node/pull/25831 for more information. PR-URL: https://github.com/nodejs/node/pull/26209 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rod Vagg <rod@vagg.org>
Diffstat (limited to 'src/node_options.h')
-rw-r--r--src/node_options.h9
1 files changed, 5 insertions, 4 deletions
diff --git a/src/node_options.h b/src/node_options.h
index e8fb002094..bcd6d2457d 100644
--- a/src/node_options.h
+++ b/src/node_options.h
@@ -121,10 +121,11 @@ class EnvironmentOptions : public Options {
bool print_eval = false;
bool force_repl = false;
-#if HAVE_OPENSSL
- bool tls_v1_0 = false;
- bool tls_v1_1 = false;
-#endif
+ bool tls_min_v1_0 = false;
+ bool tls_min_v1_1 = false;
+ bool tls_min_v1_3 = false;
+ bool tls_max_v1_2 = false;
+ bool tls_max_v1_3 = false;
std::vector<std::string> preload_modules;