summaryrefslogtreecommitdiff
path: root/test/parallel/test-tls-client-resume.js
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 /test/parallel/test-tls-client-resume.js
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 'test/parallel/test-tls-client-resume.js')
-rw-r--r--test/parallel/test-tls-client-resume.js43
1 files changed, 35 insertions, 8 deletions
diff --git a/test/parallel/test-tls-client-resume.js b/test/parallel/test-tls-client-resume.js
index 9f868fdcdc..0f5c9caa7c 100644
--- a/test/parallel/test-tls-client-resume.js
+++ b/test/parallel/test-tls-client-resume.js
@@ -44,32 +44,59 @@ const server = tls.Server(options, common.mustCall((socket) => {
// start listening
server.listen(0, common.mustCall(function() {
-
- let sessionx = null;
- let session1 = null;
+ let sessionx = null; // From right after connect, invalid for TLS1.3
+ let session1 = null; // Delivered by the session event, always valid.
+ let sessions = 0;
+ let tls13;
const client1 = tls.connect({
port: this.address().port,
rejectUnauthorized: false
}, common.mustCall(() => {
- console.log('connect1');
+ tls13 = client1.getProtocol() === 'TLSv1.3';
assert.strictEqual(client1.isSessionReused(), false);
sessionx = client1.getSession();
+ assert(sessionx);
+
+ if (session1)
+ reconnect();
+ }));
+
+ client1.on('data', common.mustCall((d) => {
}));
client1.once('session', common.mustCall((session) => {
console.log('session1');
session1 = session;
+ assert(session1);
+ if (sessionx)
+ reconnect();
}));
- client1.on('close', common.mustCall(() => {
+ client1.on('session', () => {
+ console.log('client1 session#', ++sessions);
+ });
+
+ client1.on('close', () => {
+ console.log('client1 close');
+ assert.strictEqual(sessions, tls13 ? 2 : 1);
+ });
+
+ function reconnect() {
assert(sessionx);
assert(session1);
- assert.strictEqual(sessionx.compare(session1), 0);
+ if (tls13)
+ // For TLS1.3, the session immediately after handshake is a dummy,
+ // unresumable session. The one delivered later in session event is
+ // resumable.
+ assert.notStrictEqual(sessionx.compare(session1), 0);
+ else
+ // For TLS1.2, they are identical.
+ assert.strictEqual(sessionx.compare(session1), 0);
const opts = {
port: server.address().port,
rejectUnauthorized: false,
- session: session1
+ session: session1,
};
const client2 = tls.connect(opts, common.mustCall(() => {
@@ -83,7 +110,7 @@ server.listen(0, common.mustCall(function() {
}));
client2.resume();
- }));
+ }
client1.resume();
}));