2017-01-03 22:16:48 +01:00
|
|
|
// Copyright Joyent, Inc. and other Node contributors.
|
|
|
|
//
|
|
|
|
// Permission is hereby granted, free of charge, to any person obtaining a
|
|
|
|
// copy of this software and associated documentation files (the
|
|
|
|
// "Software"), to deal in the Software without restriction, including
|
|
|
|
// without limitation the rights to use, copy, modify, merge, publish,
|
|
|
|
// distribute, sublicense, and/or sell copies of the Software, and to permit
|
|
|
|
// persons to whom the Software is furnished to do so, subject to the
|
|
|
|
// following conditions:
|
|
|
|
//
|
|
|
|
// The above copyright notice and this permission notice shall be included
|
|
|
|
// in all copies or substantial portions of the Software.
|
|
|
|
//
|
|
|
|
// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
|
|
|
|
// OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
|
|
|
|
// MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN
|
|
|
|
// NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
|
|
|
|
// DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
|
|
|
|
// OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
|
|
|
|
// USE OR OTHER DEALINGS IN THE SOFTWARE.
|
|
|
|
|
2014-11-22 16:59:48 +01:00
|
|
|
'use strict';
|
|
|
|
|
2019-03-18 17:31:43 +01:00
|
|
|
const {
|
|
|
|
assertCrypto,
|
|
|
|
deprecate
|
|
|
|
} = require('internal/util');
|
|
|
|
|
|
|
|
assertCrypto();
|
2016-03-09 00:31:31 +01:00
|
|
|
|
2019-02-06 06:45:46 +01:00
|
|
|
const assert = require('internal/assert');
|
2015-01-21 17:36:59 +01:00
|
|
|
const crypto = require('crypto');
|
|
|
|
const net = require('net');
|
|
|
|
const tls = require('tls');
|
|
|
|
const common = require('_tls_common');
|
2018-12-19 23:14:57 +01:00
|
|
|
const JSStreamSocket = require('internal/js_stream_socket');
|
2017-10-07 16:50:42 +02:00
|
|
|
const { Buffer } = require('buffer');
|
2019-03-18 17:31:43 +01:00
|
|
|
const debug = require('internal/util/debuglog').debuglog('tls');
|
2018-08-21 08:54:02 +02:00
|
|
|
const { TCP, constants: TCPConstants } = internalBinding('tcp_wrap');
|
2018-08-21 08:54:02 +02:00
|
|
|
const tls_wrap = internalBinding('tls_wrap');
|
2018-08-23 17:36:43 +02:00
|
|
|
const { Pipe, constants: PipeConstants } = internalBinding('pipe_wrap');
|
2018-07-27 14:35:39 +02:00
|
|
|
const { owner_symbol } = require('internal/async_hooks').symbols;
|
2018-08-21 08:54:02 +02:00
|
|
|
const { SecureContext: NativeSecureContext } = internalBinding('crypto');
|
2018-03-04 22:16:24 +01:00
|
|
|
const {
|
|
|
|
ERR_INVALID_ARG_TYPE,
|
2019-02-01 19:57:04 +01:00
|
|
|
ERR_INVALID_CALLBACK,
|
2018-03-04 22:16:24 +01:00
|
|
|
ERR_MULTIPLE_CALLBACK,
|
|
|
|
ERR_SOCKET_CLOSED,
|
|
|
|
ERR_TLS_DH_PARAM_SIZE,
|
|
|
|
ERR_TLS_HANDSHAKE_TIMEOUT,
|
|
|
|
ERR_TLS_RENEGOTIATE,
|
|
|
|
ERR_TLS_RENEGOTIATION_DISABLED,
|
|
|
|
ERR_TLS_REQUIRED_SERVER_NAME,
|
|
|
|
ERR_TLS_SESSION_ATTACK,
|
|
|
|
ERR_TLS_SNI_FROM_SERVER
|
|
|
|
} = require('internal/errors').codes;
|
2018-08-03 00:51:02 +02:00
|
|
|
const { validateString } = require('internal/validators');
|
2017-09-23 20:18:28 +02:00
|
|
|
const kConnectOptions = Symbol('connect-options');
|
2016-11-04 20:37:36 +01:00
|
|
|
const kDisableRenegotiation = Symbol('disable-renegotiation');
|
2017-09-23 20:18:28 +02:00
|
|
|
const kErrorEmitted = Symbol('error-emitted');
|
|
|
|
const kHandshakeTimeout = Symbol('handshake-timeout');
|
|
|
|
const kRes = Symbol('res');
|
|
|
|
const kSNICallback = Symbol('snicallback');
|
|
|
|
|
|
|
|
const noop = () => {};
|
2013-09-24 14:53:49 +02:00
|
|
|
|
2018-01-13 00:36:21 +01:00
|
|
|
let ipServernameWarned = false;
|
|
|
|
|
2019-01-31 23:41:10 +01:00
|
|
|
// Server side times how long a handshake is taking to protect against slow
|
|
|
|
// handshakes being used for DoS.
|
2018-02-04 17:51:18 +01:00
|
|
|
function onhandshakestart(now) {
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('server onhandshakestart');
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2018-05-02 12:49:13 +02:00
|
|
|
const { lastHandshakeTime } = this;
|
2018-08-31 17:42:54 +02:00
|
|
|
assert(now >= lastHandshakeTime,
|
|
|
|
`now (${now}) < lastHandshakeTime (${lastHandshakeTime})`);
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2018-05-02 12:49:13 +02:00
|
|
|
this.lastHandshakeTime = now;
|
2018-02-04 17:51:18 +01:00
|
|
|
|
2018-05-02 12:49:13 +02:00
|
|
|
// If this is the first handshake we can skip the rest of the checks.
|
|
|
|
if (lastHandshakeTime === 0)
|
|
|
|
return;
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2018-05-02 12:49:13 +02:00
|
|
|
if ((now - lastHandshakeTime) >= tls.CLIENT_RENEG_WINDOW * 1000)
|
|
|
|
this.handshakes = 1;
|
|
|
|
else
|
|
|
|
this.handshakes++;
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2018-07-27 14:35:39 +02:00
|
|
|
const owner = this[owner_symbol];
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
|
|
|
|
assert(owner._tlsOptions.isServer);
|
|
|
|
|
2018-05-02 12:49:13 +02:00
|
|
|
if (this.handshakes > tls.CLIENT_RENEG_LIMIT) {
|
|
|
|
owner._emitTLSError(new ERR_TLS_SESSION_ATTACK());
|
|
|
|
return;
|
2013-06-13 15:36:00 +02:00
|
|
|
}
|
2016-11-04 20:37:36 +01:00
|
|
|
|
2018-05-02 12:49:13 +02:00
|
|
|
if (owner[kDisableRenegotiation])
|
2018-03-04 22:16:24 +01:00
|
|
|
owner._emitTLSError(new ERR_TLS_RENEGOTIATION_DISABLED());
|
2017-09-23 20:18:28 +02:00
|
|
|
}
|
2013-06-13 15:36:00 +02:00
|
|
|
|
|
|
|
function onhandshakedone() {
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('server onhandshakedone');
|
2017-09-23 20:18:28 +02:00
|
|
|
|
2018-07-27 14:35:39 +02:00
|
|
|
const owner = this[owner_symbol];
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
assert(owner._tlsOptions.isServer);
|
2017-09-23 20:18:28 +02:00
|
|
|
|
|
|
|
// `newSession` callback wasn't called yet
|
|
|
|
if (owner._newSessionPending) {
|
|
|
|
owner._securePending = true;
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
owner._finishInit();
|
2013-06-13 15:36:00 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
function loadSession(hello) {
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('server onclienthello',
|
|
|
|
'sessionid.len', hello.sessionId.length,
|
|
|
|
'ticket?', hello.tlsTicket
|
|
|
|
);
|
2018-07-27 14:35:39 +02:00
|
|
|
const owner = this[owner_symbol];
|
2017-09-23 20:18:28 +02:00
|
|
|
|
2014-04-14 19:15:57 +02:00
|
|
|
var once = false;
|
|
|
|
function onSession(err, session) {
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('server resumeSession callback(err %j, sess? %s)', err, !!session);
|
2014-04-14 19:15:57 +02:00
|
|
|
if (once)
|
2018-03-04 22:16:24 +01:00
|
|
|
return owner.destroy(new ERR_MULTIPLE_CALLBACK());
|
2014-04-14 19:15:57 +02:00
|
|
|
once = true;
|
2013-06-17 12:11:13 +02:00
|
|
|
|
|
|
|
if (err)
|
2017-09-23 20:18:28 +02:00
|
|
|
return owner.destroy(err);
|
2013-06-17 12:11:13 +02:00
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
if (owner._handle === null)
|
2018-03-04 22:16:24 +01:00
|
|
|
return owner.destroy(new ERR_SOCKET_CLOSED());
|
2015-05-14 10:38:18 +02:00
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
owner._handle.loadSession(session);
|
2019-01-31 23:41:10 +01:00
|
|
|
// Session is loaded. End the parser to allow handshaking to continue.
|
2017-09-23 20:18:28 +02:00
|
|
|
owner._handle.endParser();
|
2014-04-14 19:15:57 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
if (hello.sessionId.length <= 0 ||
|
|
|
|
hello.tlsTicket ||
|
2017-09-23 20:18:28 +02:00
|
|
|
owner.server &&
|
|
|
|
!owner.server.emit('resumeSession', hello.sessionId, onSession)) {
|
2019-01-31 23:41:10 +01:00
|
|
|
// Sessions without identifiers can't be resumed.
|
|
|
|
// Sessions with tickets can be resumed directly from the ticket, no server
|
|
|
|
// session storage is necessary.
|
|
|
|
// Without a call to a resumeSession listener, a session will never be
|
|
|
|
// loaded, so end the parser to allow handshaking to continue.
|
2017-09-23 20:18:28 +02:00
|
|
|
owner._handle.endParser();
|
2014-04-14 19:15:57 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
function loadSNI(info) {
|
2018-07-27 14:35:39 +02:00
|
|
|
const owner = this[owner_symbol];
|
2017-09-23 20:18:28 +02:00
|
|
|
const servername = info.servername;
|
|
|
|
if (!servername || !owner._SNICallback)
|
|
|
|
return requestOCSP(owner, info);
|
2014-04-14 19:15:57 +02:00
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
let once = false;
|
|
|
|
owner._SNICallback(servername, (err, context) => {
|
2014-04-14 19:15:57 +02:00
|
|
|
if (once)
|
2018-03-04 22:16:24 +01:00
|
|
|
return owner.destroy(new ERR_MULTIPLE_CALLBACK());
|
2014-04-14 19:15:57 +02:00
|
|
|
once = true;
|
|
|
|
|
|
|
|
if (err)
|
2017-09-23 20:18:28 +02:00
|
|
|
return owner.destroy(err);
|
2014-04-14 19:15:57 +02:00
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
if (owner._handle === null)
|
2018-03-04 22:16:24 +01:00
|
|
|
return owner.destroy(new ERR_SOCKET_CLOSED());
|
2015-05-14 10:38:18 +02:00
|
|
|
|
2014-04-14 19:15:57 +02:00
|
|
|
// TODO(indutny): eventually disallow raw `SecureContext`
|
|
|
|
if (context)
|
2017-09-23 20:18:28 +02:00
|
|
|
owner._handle.sni_context = context.context || context;
|
2014-04-14 19:15:57 +02:00
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
requestOCSP(owner, info);
|
2014-04-14 19:15:57 +02:00
|
|
|
});
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
function requestOCSP(socket, info) {
|
|
|
|
if (!info.OCSPRequest || !socket.server)
|
|
|
|
return requestOCSPDone(socket);
|
2014-04-14 19:15:57 +02:00
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
let ctx = socket._handle.sni_context;
|
2017-01-09 14:38:31 +01:00
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
if (!ctx) {
|
|
|
|
ctx = socket.server._sharedCreds;
|
|
|
|
|
|
|
|
// TLS socket is using a `net.Server` instead of a tls.TLSServer.
|
|
|
|
// Some TLS properties like `server._sharedCreds` will not be present
|
|
|
|
if (!ctx)
|
|
|
|
return requestOCSPDone(socket);
|
|
|
|
}
|
2017-01-09 14:38:31 +01:00
|
|
|
|
|
|
|
// TODO(indutny): eventually disallow raw `SecureContext`
|
2014-04-14 19:15:57 +02:00
|
|
|
if (ctx.context)
|
|
|
|
ctx = ctx.context;
|
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
if (socket.server.listenerCount('OCSPRequest') === 0) {
|
|
|
|
return requestOCSPDone(socket);
|
2014-04-14 19:15:57 +02:00
|
|
|
}
|
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
let once = false;
|
|
|
|
const onOCSP = (err, response) => {
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('server OCSPRequest done', 'handle?', !!socket._handle, 'once?', once,
|
|
|
|
'response?', !!response, 'err?', err);
|
2014-04-14 19:15:57 +02:00
|
|
|
if (once)
|
2018-03-04 22:16:24 +01:00
|
|
|
return socket.destroy(new ERR_MULTIPLE_CALLBACK());
|
2014-04-14 19:15:57 +02:00
|
|
|
once = true;
|
|
|
|
|
|
|
|
if (err)
|
2017-09-23 20:18:28 +02:00
|
|
|
return socket.destroy(err);
|
2014-04-14 19:15:57 +02:00
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
if (socket._handle === null)
|
2018-03-04 22:16:24 +01:00
|
|
|
return socket.destroy(new ERR_SOCKET_CLOSED());
|
2015-05-14 10:38:18 +02:00
|
|
|
|
2014-04-14 19:15:57 +02:00
|
|
|
if (response)
|
2017-09-23 20:18:28 +02:00
|
|
|
socket._handle.setOCSPResponse(response);
|
|
|
|
requestOCSPDone(socket);
|
|
|
|
};
|
2014-04-14 19:15:57 +02:00
|
|
|
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('server oncertcb emit OCSPRequest');
|
2017-09-23 20:18:28 +02:00
|
|
|
socket.server.emit('OCSPRequest',
|
|
|
|
ctx.getCertificate(),
|
|
|
|
ctx.getIssuer(),
|
|
|
|
onOCSP);
|
2015-04-18 10:19:23 +02:00
|
|
|
}
|
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
function requestOCSPDone(socket) {
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('server certcb done');
|
2017-09-23 20:18:28 +02:00
|
|
|
try {
|
|
|
|
socket._handle.certCbDone();
|
|
|
|
} catch (e) {
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('server certcb done errored', e);
|
2017-09-23 20:18:28 +02:00
|
|
|
socket.destroy(e);
|
|
|
|
}
|
2013-06-17 12:11:13 +02:00
|
|
|
}
|
|
|
|
|
2019-01-30 21:18:04 +01:00
|
|
|
function onnewsessionclient(sessionId, session) {
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('client emit session');
|
2019-01-30 21:18:04 +01:00
|
|
|
const owner = this[owner_symbol];
|
|
|
|
owner.emit('session', session);
|
|
|
|
}
|
|
|
|
|
2018-12-19 23:45:51 +01:00
|
|
|
function onnewsession(sessionId, session) {
|
2019-01-31 23:41:10 +01:00
|
|
|
debug('onnewsession');
|
2018-07-27 14:35:39 +02:00
|
|
|
const owner = this[owner_symbol];
|
2017-09-23 20:18:28 +02:00
|
|
|
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
// TODO(@sam-github) no server to emit the event on, but handshake won't
|
|
|
|
// continue unless newSessionDone() is called, should it be, or is that
|
|
|
|
// situation unreachable, or only occurring during shutdown?
|
2017-09-23 20:18:28 +02:00
|
|
|
if (!owner.server)
|
2014-02-14 14:01:34 +01:00
|
|
|
return;
|
|
|
|
|
|
|
|
var once = false;
|
2017-09-23 20:18:28 +02:00
|
|
|
const done = () => {
|
2019-01-31 23:41:10 +01:00
|
|
|
debug('onnewsession done');
|
2014-02-14 14:01:34 +01:00
|
|
|
if (once)
|
|
|
|
return;
|
|
|
|
once = true;
|
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
if (owner._handle === null)
|
2018-03-04 22:16:24 +01:00
|
|
|
return owner.destroy(new ERR_SOCKET_CLOSED());
|
2015-05-14 10:38:18 +02:00
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
this.newSessionDone();
|
2014-02-14 14:01:34 +01:00
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
owner._newSessionPending = false;
|
|
|
|
if (owner._securePending)
|
|
|
|
owner._finishInit();
|
|
|
|
owner._securePending = false;
|
|
|
|
};
|
|
|
|
|
|
|
|
owner._newSessionPending = true;
|
2018-12-19 23:45:51 +01:00
|
|
|
if (!owner.server.emit('newSession', sessionId, session, done))
|
2017-09-23 20:18:28 +02:00
|
|
|
done();
|
2013-06-17 12:11:13 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2014-04-14 19:15:57 +02:00
|
|
|
function onocspresponse(resp) {
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('client onocspresponse');
|
2018-07-27 14:35:39 +02:00
|
|
|
this[owner_symbol].emit('OCSPResponse', resp);
|
2017-09-23 20:18:28 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
function onerror(err) {
|
2018-07-27 14:35:39 +02:00
|
|
|
const owner = this[owner_symbol];
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('%s onerror %s had? %j',
|
|
|
|
owner._tlsOptions.isServer ? 'server' : 'client', err,
|
|
|
|
owner._hadError);
|
2017-09-23 20:18:28 +02:00
|
|
|
|
2018-10-13 06:59:35 +02:00
|
|
|
if (owner._hadError)
|
2017-09-23 20:18:28 +02:00
|
|
|
return;
|
|
|
|
|
2018-10-13 06:59:35 +02:00
|
|
|
owner._hadError = true;
|
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
// Destroy socket if error happened before handshake's finish
|
|
|
|
if (!owner._secureEstablished) {
|
|
|
|
// When handshake fails control is not yet released,
|
|
|
|
// so self._tlsError will return null instead of actual error
|
|
|
|
owner.destroy(err);
|
|
|
|
} else if (owner._tlsOptions.isServer &&
|
|
|
|
owner._rejectUnauthorized &&
|
|
|
|
/peer did not return a certificate/.test(err.message)) {
|
|
|
|
// Ignore server's authorization errors
|
|
|
|
owner.destroy();
|
|
|
|
} else {
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
// Emit error
|
2017-09-23 20:18:28 +02:00
|
|
|
owner._emitTLSError(err);
|
|
|
|
}
|
2014-04-14 19:15:57 +02:00
|
|
|
}
|
|
|
|
|
2018-12-19 23:30:20 +01:00
|
|
|
// Used by both client and server TLSSockets to start data flowing from _handle,
|
|
|
|
// read(0) causes a StreamBase::ReadStart, via Socket._read.
|
2019-01-31 23:07:36 +01:00
|
|
|
function initRead(tlsSocket, socket) {
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('%s initRead',
|
|
|
|
tlsSocket._tlsOptions.isServer ? 'server' : 'client',
|
|
|
|
'handle?', !!tlsSocket._handle,
|
|
|
|
'buffered?', !!socket && socket.readableLength
|
|
|
|
);
|
2015-06-09 00:25:06 +02:00
|
|
|
// If we were destroyed already don't bother reading
|
2019-01-31 23:07:36 +01:00
|
|
|
if (!tlsSocket._handle)
|
2015-06-09 00:25:06 +02:00
|
|
|
return;
|
|
|
|
|
|
|
|
// Socket already has some buffered data - emulate receiving it
|
2018-12-19 23:30:20 +01:00
|
|
|
if (socket && socket.readableLength) {
|
2015-06-09 00:25:06 +02:00
|
|
|
var buf;
|
2018-12-19 23:30:20 +01:00
|
|
|
while ((buf = socket.read()) !== null)
|
2019-01-31 23:07:36 +01:00
|
|
|
tlsSocket._handle.receive(buf);
|
2015-06-09 00:25:06 +02:00
|
|
|
}
|
|
|
|
|
2019-01-31 23:07:36 +01:00
|
|
|
tlsSocket.read(0);
|
2015-06-09 00:25:06 +02:00
|
|
|
}
|
2014-04-14 19:15:57 +02:00
|
|
|
|
2013-06-13 15:36:00 +02:00
|
|
|
/**
|
|
|
|
* Provides a wrap of socket stream to do encrypted communication.
|
|
|
|
*/
|
|
|
|
|
2017-10-31 21:03:28 +01:00
|
|
|
function TLSSocket(socket, opts) {
|
2018-12-18 02:28:09 +01:00
|
|
|
const tlsOptions = { ...opts };
|
2017-10-31 21:03:28 +01:00
|
|
|
|
|
|
|
if (tlsOptions.ALPNProtocols)
|
|
|
|
tls.convertALPNProtocols(tlsOptions.ALPNProtocols, tlsOptions);
|
|
|
|
|
|
|
|
this._tlsOptions = tlsOptions;
|
2013-06-13 15:36:00 +02:00
|
|
|
this._secureEstablished = false;
|
2014-02-14 14:01:34 +01:00
|
|
|
this._securePending = false;
|
|
|
|
this._newSessionPending = false;
|
2013-06-13 15:36:00 +02:00
|
|
|
this._controlReleased = false;
|
2013-08-03 19:29:54 +02:00
|
|
|
this._SNICallback = null;
|
2013-06-13 15:36:00 +02:00
|
|
|
this.servername = null;
|
2015-04-23 08:25:15 +02:00
|
|
|
this.alpnProtocol = null;
|
2013-06-13 15:36:00 +02:00
|
|
|
this.authorized = false;
|
|
|
|
this.authorizationError = null;
|
2017-09-23 20:18:28 +02:00
|
|
|
this[kRes] = null;
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2015-03-03 21:17:43 +01:00
|
|
|
var wrap;
|
2018-11-10 21:11:17 +01:00
|
|
|
if ((socket instanceof net.Socket && socket._handle) || !socket) {
|
2019-01-31 23:41:10 +01:00
|
|
|
// 1. connected socket
|
|
|
|
// 2. no socket, one will be created with net.Socket().connect
|
2015-03-03 21:17:43 +01:00
|
|
|
wrap = socket;
|
2018-11-10 21:11:17 +01:00
|
|
|
} else {
|
2019-01-31 23:41:10 +01:00
|
|
|
// 3. socket has no handle so it is js not c++
|
|
|
|
// 4. unconnected sockets are wrapped
|
2018-12-19 23:14:57 +01:00
|
|
|
// TLS expects to interact from C++ with a net.Socket that has a C++ stream
|
|
|
|
// handle, but a JS stream doesn't have one. Wrap it up to make it look like
|
|
|
|
// a socket.
|
|
|
|
wrap = new JSStreamSocket(socket);
|
2018-11-10 21:11:17 +01:00
|
|
|
wrap.once('close', () => this.destroy());
|
|
|
|
}
|
2015-02-23 21:09:44 +01:00
|
|
|
|
2013-12-19 10:04:34 +01:00
|
|
|
// Just a documented property to make secure sockets
|
|
|
|
// distinguishable from regular ones.
|
|
|
|
this.encrypted = true;
|
|
|
|
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
net.Socket.call(this, {
|
2015-06-07 00:37:35 +02:00
|
|
|
handle: this._wrapHandle(wrap),
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
allowHalfOpen: socket && socket.allowHalfOpen,
|
|
|
|
readable: false,
|
|
|
|
writable: false
|
|
|
|
});
|
|
|
|
|
|
|
|
// Proxy for API compatibility
|
2019-01-31 23:41:10 +01:00
|
|
|
this.ssl = this._handle; // C++ TLSWrap object
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
|
2016-10-01 21:17:51 +02:00
|
|
|
this.on('error', this._tlsError);
|
2013-08-07 14:50:36 +02:00
|
|
|
|
2015-03-03 21:17:43 +01:00
|
|
|
this._init(socket, wrap);
|
2014-04-14 12:12:35 +02:00
|
|
|
|
2016-04-26 22:27:08 +02:00
|
|
|
// Make sure to setup all required properties like: `connecting` before
|
2014-04-14 12:12:35 +02:00
|
|
|
// starting the flow of the data
|
|
|
|
this.readable = true;
|
|
|
|
this.writable = true;
|
2015-06-09 00:25:06 +02:00
|
|
|
|
|
|
|
// Read on next tick so the caller has a chance to setup listeners
|
|
|
|
process.nextTick(initRead, this, socket);
|
2013-06-13 15:36:00 +02:00
|
|
|
}
|
2019-03-18 17:31:43 +01:00
|
|
|
Object.setPrototypeOf(TLSSocket.prototype, net.Socket.prototype);
|
|
|
|
Object.setPrototypeOf(TLSSocket, net.Socket);
|
2013-07-03 09:46:01 +02:00
|
|
|
exports.TLSSocket = TLSSocket;
|
2013-06-13 15:36:00 +02:00
|
|
|
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
var proxiedMethods = [
|
2015-06-07 00:37:35 +02:00
|
|
|
'ref', 'unref', 'open', 'bind', 'listen', 'connect', 'bind6',
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
'connect6', 'getsockname', 'getpeername', 'setNoDelay', 'setKeepAlive',
|
|
|
|
'setSimultaneousAccepts', 'setBlocking',
|
2013-06-13 15:36:00 +02:00
|
|
|
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
// PipeWrap
|
|
|
|
'setPendingInstances'
|
|
|
|
];
|
|
|
|
|
2015-03-09 15:50:29 +01:00
|
|
|
// Proxy HandleWrap, PipeWrap and TCPWrap methods
|
2017-02-26 07:41:45 +01:00
|
|
|
function makeMethodProxy(name) {
|
|
|
|
return function methodProxy(...args) {
|
2015-03-09 15:50:29 +01:00
|
|
|
if (this._parent[name])
|
2017-02-13 22:26:42 +01:00
|
|
|
return this._parent[name].apply(this._parent, args);
|
2015-03-09 15:50:29 +01:00
|
|
|
};
|
2017-02-26 07:41:45 +01:00
|
|
|
}
|
|
|
|
for (var n = 0; n < proxiedMethods.length; n++) {
|
|
|
|
tls_wrap.TLSWrap.prototype[proxiedMethods[n]] =
|
|
|
|
makeMethodProxy(proxiedMethods[n]);
|
|
|
|
}
|
2015-03-09 15:50:29 +01:00
|
|
|
|
2016-10-16 00:02:43 +02:00
|
|
|
tls_wrap.TLSWrap.prototype.close = function close(cb) {
|
2016-11-12 22:08:59 +01:00
|
|
|
let ssl;
|
2018-07-27 14:35:39 +02:00
|
|
|
if (this[owner_symbol]) {
|
|
|
|
ssl = this[owner_symbol].ssl;
|
|
|
|
this[owner_symbol].ssl = null;
|
2016-11-12 22:08:59 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
// Invoke `destroySSL` on close to clean up possibly pending write requests
|
|
|
|
// that may self-reference TLSWrap, leading to leak
|
|
|
|
const done = () => {
|
|
|
|
if (ssl) {
|
|
|
|
ssl.destroySSL();
|
|
|
|
if (ssl._secureContext.singleUse) {
|
|
|
|
ssl._secureContext.context.close();
|
|
|
|
ssl._secureContext.context = null;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if (cb)
|
|
|
|
cb();
|
|
|
|
};
|
2016-02-09 22:00:24 +01:00
|
|
|
|
2015-06-07 00:37:35 +02:00
|
|
|
if (this._parentWrap && this._parentWrap._handle === this._parent) {
|
2016-11-12 22:08:59 +01:00
|
|
|
this._parentWrap.once('close', done);
|
2015-06-07 00:37:35 +02:00
|
|
|
return this._parentWrap.destroy();
|
|
|
|
}
|
2016-11-12 22:08:59 +01:00
|
|
|
return this._parent.close(done);
|
2015-06-07 00:37:35 +02:00
|
|
|
};
|
|
|
|
|
2016-11-04 20:37:36 +01:00
|
|
|
TLSSocket.prototype.disableRenegotiation = function disableRenegotiation() {
|
|
|
|
this[kDisableRenegotiation] = true;
|
|
|
|
};
|
|
|
|
|
2015-06-07 00:37:35 +02:00
|
|
|
TLSSocket.prototype._wrapHandle = function(wrap) {
|
|
|
|
var handle;
|
|
|
|
|
|
|
|
if (wrap)
|
|
|
|
handle = wrap._handle;
|
2013-06-13 15:36:00 +02:00
|
|
|
|
|
|
|
var options = this._tlsOptions;
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
if (!handle) {
|
2017-11-20 17:18:40 +01:00
|
|
|
handle = options.pipe ?
|
|
|
|
new Pipe(PipeConstants.SOCKET) :
|
|
|
|
new TCP(TCPConstants.SOCKET);
|
2018-07-27 14:35:39 +02:00
|
|
|
handle[owner_symbol] = this;
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
}
|
2013-06-13 15:36:00 +02:00
|
|
|
|
|
|
|
// Wrap socket's handle
|
2017-09-23 20:18:28 +02:00
|
|
|
const context = options.secureContext ||
|
|
|
|
options.credentials ||
|
|
|
|
tls.createSecureContext(options);
|
2019-03-08 09:47:45 +01:00
|
|
|
assert(handle.isStreamBase, 'handle must be a StreamBase');
|
2018-01-10 18:42:08 +01:00
|
|
|
assert(context.context instanceof NativeSecureContext,
|
|
|
|
'context.context must be a NativeSecureContext');
|
2019-03-08 09:47:45 +01:00
|
|
|
const res = tls_wrap.wrap(handle, context.context, !!options.isServer);
|
2019-01-31 23:41:10 +01:00
|
|
|
res._parent = handle; // C++ "wrap" object: TCPWrap, JSStream, ...
|
|
|
|
res._parentWrap = wrap; // JS object: net.Socket, JSStreamSocket, ...
|
2015-03-06 02:27:58 +01:00
|
|
|
res._secureContext = context;
|
2015-02-28 00:07:25 +01:00
|
|
|
res.reading = handle.reading;
|
2017-09-23 20:18:28 +02:00
|
|
|
this[kRes] = res;
|
|
|
|
defineHandleReading(this, handle);
|
|
|
|
|
|
|
|
this.on('close', onSocketCloseDestroySSL);
|
|
|
|
|
|
|
|
return res;
|
|
|
|
};
|
|
|
|
|
|
|
|
// This eliminates a cyclic reference to TLSWrap
|
|
|
|
// Ref: https://github.com/nodejs/node/commit/f7620fb96d339f704932f9bb9a0dceb9952df2d4
|
|
|
|
function defineHandleReading(socket, handle) {
|
2015-02-28 19:14:07 +01:00
|
|
|
Object.defineProperty(handle, 'reading', {
|
2017-09-23 20:18:28 +02:00
|
|
|
get: () => {
|
|
|
|
return socket[kRes].reading;
|
2015-02-28 19:14:07 +01:00
|
|
|
},
|
2017-09-23 20:18:28 +02:00
|
|
|
set: (value) => {
|
|
|
|
socket[kRes].reading = value;
|
2015-02-28 19:14:07 +01:00
|
|
|
}
|
|
|
|
});
|
2017-09-23 20:18:28 +02:00
|
|
|
}
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
function onSocketCloseDestroySSL() {
|
|
|
|
// Make sure we are not doing it on OpenSSL's stack
|
|
|
|
setImmediate(destroySSL, this);
|
|
|
|
this[kRes] = null;
|
|
|
|
}
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
|
2015-05-18 20:24:19 +02:00
|
|
|
function destroySSL(self) {
|
|
|
|
self._destroySSL();
|
|
|
|
}
|
|
|
|
|
2015-04-26 14:26:57 +02:00
|
|
|
TLSSocket.prototype._destroySSL = function _destroySSL() {
|
2015-05-01 23:59:05 +02:00
|
|
|
if (!this.ssl) return;
|
2015-04-27 09:39:48 +02:00
|
|
|
this.ssl.destroySSL();
|
2015-05-01 23:59:05 +02:00
|
|
|
if (this.ssl._secureContext.singleUse) {
|
2015-04-27 09:39:48 +02:00
|
|
|
this.ssl._secureContext.context.close();
|
2015-05-01 23:59:05 +02:00
|
|
|
this.ssl._secureContext.context = null;
|
|
|
|
}
|
|
|
|
this.ssl = null;
|
2015-04-26 14:26:57 +02:00
|
|
|
};
|
|
|
|
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
// Constructor guts, arbitrarily factored out.
|
2015-03-03 21:17:43 +01:00
|
|
|
TLSSocket.prototype._init = function(socket, wrap) {
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
var options = this._tlsOptions;
|
|
|
|
var ssl = this._handle;
|
2015-06-07 00:37:35 +02:00
|
|
|
this.server = options.server;
|
|
|
|
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('%s _init',
|
|
|
|
options.isServer ? 'server' : 'client',
|
|
|
|
'handle?', !!ssl
|
|
|
|
);
|
|
|
|
|
2019-01-31 23:41:10 +01:00
|
|
|
// Clients (!isServer) always request a cert, servers request a client cert
|
|
|
|
// only on explicit configuration.
|
2016-01-12 22:04:50 +01:00
|
|
|
const requestCert = !!options.requestCert || !options.isServer;
|
|
|
|
const rejectUnauthorized = !!options.rejectUnauthorized;
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2013-08-23 15:53:16 +02:00
|
|
|
this._requestCert = requestCert;
|
|
|
|
this._rejectUnauthorized = rejectUnauthorized;
|
2013-06-13 15:36:00 +02:00
|
|
|
if (requestCert || rejectUnauthorized)
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
ssl.setVerifyMode(requestCert, rejectUnauthorized);
|
2013-06-13 15:36:00 +02:00
|
|
|
|
|
|
|
if (options.isServer) {
|
2017-09-23 20:18:28 +02:00
|
|
|
ssl.onhandshakestart = onhandshakestart;
|
|
|
|
ssl.onhandshakedone = onhandshakedone;
|
|
|
|
ssl.onclienthello = loadSession;
|
|
|
|
ssl.oncertcb = loadSNI;
|
|
|
|
ssl.onnewsession = onnewsession;
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
ssl.lastHandshakeTime = 0;
|
|
|
|
ssl.handshakes = 0;
|
2013-06-17 12:11:13 +02:00
|
|
|
|
2015-04-18 10:19:23 +02:00
|
|
|
if (this.server) {
|
2015-08-11 20:31:50 +02:00
|
|
|
if (this.server.listenerCount('resumeSession') > 0 ||
|
|
|
|
this.server.listenerCount('newSession') > 0) {
|
2019-01-31 23:41:10 +01:00
|
|
|
// Also starts the client hello parser as a side effect.
|
2015-04-18 10:19:23 +02:00
|
|
|
ssl.enableSessionCallbacks();
|
|
|
|
}
|
2015-08-11 20:31:50 +02:00
|
|
|
if (this.server.listenerCount('OCSPRequest') > 0)
|
2015-04-18 10:19:23 +02:00
|
|
|
ssl.enableCertCb();
|
2013-06-17 12:11:13 +02:00
|
|
|
}
|
2013-06-13 15:36:00 +02:00
|
|
|
} else {
|
2017-09-23 20:18:28 +02:00
|
|
|
ssl.onhandshakestart = noop;
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
ssl.onhandshakedone = () => {
|
|
|
|
debug('client onhandshakedone');
|
|
|
|
this._finishInit();
|
|
|
|
};
|
2017-09-23 20:18:28 +02:00
|
|
|
ssl.onocspresponse = onocspresponse;
|
2014-02-03 22:32:13 +01:00
|
|
|
|
|
|
|
if (options.session)
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
ssl.setSession(options.session);
|
2019-01-30 21:18:04 +01:00
|
|
|
|
|
|
|
ssl.onnewsession = onnewsessionclient;
|
|
|
|
|
|
|
|
// Only call .onnewsession if there is a session listener.
|
|
|
|
this.on('newListener', newListener);
|
|
|
|
|
|
|
|
function newListener(event) {
|
|
|
|
if (event !== 'session')
|
|
|
|
return;
|
|
|
|
|
|
|
|
ssl.enableSessionCallbacks();
|
|
|
|
|
|
|
|
// Remover this listener since its no longer needed.
|
|
|
|
this.removeListener('newListener', newListener);
|
|
|
|
}
|
2013-06-13 15:36:00 +02:00
|
|
|
}
|
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
ssl.onerror = onerror;
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2013-08-02 18:11:17 +02:00
|
|
|
// If custom SNICallback was given, or if
|
|
|
|
// there're SNI contexts to perform match against -
|
|
|
|
// set `.onsniselect` callback.
|
2018-06-02 10:52:59 +02:00
|
|
|
if (options.isServer &&
|
2015-06-07 00:37:35 +02:00
|
|
|
options.SNICallback &&
|
2013-08-02 18:11:17 +02:00
|
|
|
(options.SNICallback !== SNICallback ||
|
2017-12-23 09:01:58 +01:00
|
|
|
(options.server && options.server._contexts.length))) {
|
2013-08-02 18:11:17 +02:00
|
|
|
assert(typeof options.SNICallback === 'function');
|
2013-08-03 19:29:54 +02:00
|
|
|
this._SNICallback = options.SNICallback;
|
2015-04-18 10:19:23 +02:00
|
|
|
ssl.enableCertCb();
|
2013-06-13 15:36:00 +02:00
|
|
|
}
|
|
|
|
|
2018-06-02 10:52:59 +02:00
|
|
|
if (options.ALPNProtocols) {
|
2019-01-21 01:22:27 +01:00
|
|
|
// Keep reference in secureContext not to be GC-ed
|
2015-04-23 08:25:15 +02:00
|
|
|
ssl._secureContext.alpnBuffer = options.ALPNProtocols;
|
|
|
|
ssl.setALPNProtocols(ssl._secureContext.alpnBuffer);
|
|
|
|
}
|
|
|
|
|
2013-08-23 15:53:16 +02:00
|
|
|
if (options.handshakeTimeout > 0)
|
|
|
|
this.setTimeout(options.handshakeTimeout, this._handleTimeout);
|
2014-01-23 13:55:28 +01:00
|
|
|
|
2015-03-03 21:17:43 +01:00
|
|
|
if (socket instanceof net.Socket) {
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
this._parent = socket;
|
|
|
|
|
|
|
|
// To prevent assertion in afterConnect() and properly kick off readStart
|
2016-04-26 22:27:08 +02:00
|
|
|
this.connecting = socket.connecting || !socket._handle;
|
2017-09-23 20:18:28 +02:00
|
|
|
socket.once('connect', () => {
|
|
|
|
this.connecting = false;
|
|
|
|
this.emit('connect');
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
});
|
2014-01-23 13:55:28 +01:00
|
|
|
}
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
|
|
|
|
// Assume `tls.connect()`
|
2015-03-03 21:17:43 +01:00
|
|
|
if (wrap) {
|
2017-09-23 20:18:28 +02:00
|
|
|
wrap.on('error', (err) => this._emitTLSError(err));
|
2015-03-03 21:17:43 +01:00
|
|
|
} else {
|
|
|
|
assert(!socket);
|
2016-04-26 22:27:08 +02:00
|
|
|
this.connecting = true;
|
2015-03-03 21:17:43 +01:00
|
|
|
}
|
2013-08-23 15:53:16 +02:00
|
|
|
};
|
|
|
|
|
|
|
|
TLSSocket.prototype.renegotiate = function(options, callback) {
|
2019-02-01 19:57:04 +01:00
|
|
|
if (options === null || typeof options !== 'object')
|
|
|
|
throw new ERR_INVALID_ARG_TYPE('options', 'Object', options);
|
2019-02-04 19:13:18 +01:00
|
|
|
if (callback !== undefined && typeof callback !== 'function')
|
2019-02-01 19:57:04 +01:00
|
|
|
throw new ERR_INVALID_CALLBACK();
|
|
|
|
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('%s renegotiate()',
|
|
|
|
this._tlsOptions.isServer ? 'server' : 'client',
|
|
|
|
'destroyed?', this.destroyed
|
|
|
|
);
|
|
|
|
|
2015-04-26 14:26:57 +02:00
|
|
|
if (this.destroyed)
|
|
|
|
return;
|
|
|
|
|
2018-01-10 18:42:08 +01:00
|
|
|
let requestCert = !!this._requestCert;
|
|
|
|
let rejectUnauthorized = !!this._rejectUnauthorized;
|
2017-09-23 20:18:28 +02:00
|
|
|
|
|
|
|
if (options.requestCert !== undefined)
|
2013-08-23 15:53:16 +02:00
|
|
|
requestCert = !!options.requestCert;
|
2017-09-23 20:18:28 +02:00
|
|
|
if (options.rejectUnauthorized !== undefined)
|
2013-08-23 15:53:16 +02:00
|
|
|
rejectUnauthorized = !!options.rejectUnauthorized;
|
|
|
|
|
|
|
|
if (requestCert !== this._requestCert ||
|
|
|
|
rejectUnauthorized !== this._rejectUnauthorized) {
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
this._handle.setVerifyMode(requestCert, rejectUnauthorized);
|
2013-08-23 15:53:16 +02:00
|
|
|
this._requestCert = requestCert;
|
|
|
|
this._rejectUnauthorized = rejectUnauthorized;
|
|
|
|
}
|
2019-02-07 22:27:14 +01:00
|
|
|
// Ensure that we'll cycle through internal openssl's state
|
|
|
|
this.write('');
|
|
|
|
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
if (!this._handle.renegotiate()) {
|
2013-08-23 15:53:16 +02:00
|
|
|
if (callback) {
|
2018-03-04 22:16:24 +01:00
|
|
|
process.nextTick(callback, new ERR_TLS_RENEGOTIATE());
|
2013-08-23 15:53:16 +02:00
|
|
|
}
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
// Ensure that we'll cycle through internal openssl's state
|
|
|
|
this.write('');
|
|
|
|
|
|
|
|
if (callback) {
|
2017-09-23 20:18:28 +02:00
|
|
|
this.once('secure', () => callback(null));
|
2013-08-23 15:53:16 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
return true;
|
|
|
|
};
|
|
|
|
|
2014-01-17 19:46:49 +01:00
|
|
|
TLSSocket.prototype.setMaxSendFragment = function setMaxSendFragment(size) {
|
2016-11-30 00:58:05 +01:00
|
|
|
return this._handle.setMaxSendFragment(size) === 1;
|
2014-01-17 19:46:49 +01:00
|
|
|
};
|
|
|
|
|
2013-08-23 15:53:16 +02:00
|
|
|
TLSSocket.prototype._handleTimeout = function() {
|
2018-03-04 22:16:24 +01:00
|
|
|
this._emitTLSError(new ERR_TLS_HANDSHAKE_TIMEOUT());
|
2015-05-15 21:21:06 +02:00
|
|
|
};
|
|
|
|
|
|
|
|
TLSSocket.prototype._emitTLSError = function(err) {
|
|
|
|
var e = this._tlsError(err);
|
|
|
|
if (e)
|
|
|
|
this.emit('error', e);
|
2013-06-13 15:36:00 +02:00
|
|
|
};
|
|
|
|
|
|
|
|
TLSSocket.prototype._tlsError = function(err) {
|
|
|
|
this.emit('_tlsError', err);
|
|
|
|
if (this._controlReleased)
|
2015-05-15 21:21:06 +02:00
|
|
|
return err;
|
|
|
|
return null;
|
2013-06-13 15:36:00 +02:00
|
|
|
};
|
|
|
|
|
2013-08-07 14:50:36 +02:00
|
|
|
TLSSocket.prototype._releaseControl = function() {
|
|
|
|
if (this._controlReleased)
|
2013-08-23 15:53:16 +02:00
|
|
|
return false;
|
2013-08-07 14:50:36 +02:00
|
|
|
this._controlReleased = true;
|
2016-10-01 21:17:51 +02:00
|
|
|
this.removeListener('error', this._tlsError);
|
2013-08-23 15:53:16 +02:00
|
|
|
return true;
|
2013-08-07 14:50:36 +02:00
|
|
|
};
|
|
|
|
|
2013-06-13 15:36:00 +02:00
|
|
|
TLSSocket.prototype._finishInit = function() {
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
// Guard against getting onhandshakedone() after .destroy().
|
|
|
|
// * 1.2: If destroy() during onocspresponse(), then write of next handshake
|
|
|
|
// record fails, the handshake done info callbacks does not occur, and the
|
|
|
|
// socket closes.
|
|
|
|
// * 1.3: The OCSP response comes in the same record that finishes handshake,
|
|
|
|
// so even after .destroy(), the handshake done info callback occurs
|
|
|
|
// immediately after onocspresponse(). Ignore it.
|
|
|
|
if (!this._handle)
|
|
|
|
return;
|
|
|
|
|
2018-06-02 10:52:59 +02:00
|
|
|
this.alpnProtocol = this._handle.getALPNNegotiatedProtocol();
|
|
|
|
this.servername = this._handle.getServername();
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
|
|
|
|
debug('%s _finishInit',
|
|
|
|
this._tlsOptions.isServer ? 'server' : 'client',
|
|
|
|
'handle?', !!this._handle,
|
|
|
|
'alpn', this.alpnProtocol,
|
|
|
|
'servername', this.servername);
|
|
|
|
|
2013-06-13 15:36:00 +02:00
|
|
|
this._secureEstablished = true;
|
2013-08-23 15:53:16 +02:00
|
|
|
if (this._tlsOptions.handshakeTimeout > 0)
|
|
|
|
this.setTimeout(0, this._handleTimeout);
|
2013-06-13 15:36:00 +02:00
|
|
|
this.emit('secure');
|
|
|
|
};
|
|
|
|
|
|
|
|
TLSSocket.prototype._start = function() {
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('%s _start',
|
|
|
|
this._tlsOptions.isServer ? 'server' : 'client',
|
|
|
|
'handle?', !!this._handle,
|
|
|
|
'connecting?', this.connecting,
|
|
|
|
'requestOCSP?', !!this._tlsOptions.requestOCSP,
|
|
|
|
);
|
2016-04-26 22:27:08 +02:00
|
|
|
if (this.connecting) {
|
2017-09-23 20:18:28 +02:00
|
|
|
this.once('connect', this._start);
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2015-06-07 00:37:35 +02:00
|
|
|
// Socket was destroyed before the connection was established
|
|
|
|
if (!this._handle)
|
|
|
|
return;
|
|
|
|
|
2014-04-14 19:15:57 +02:00
|
|
|
if (this._tlsOptions.requestOCSP)
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
this._handle.requestOCSP();
|
|
|
|
this._handle.start();
|
2013-06-13 15:36:00 +02:00
|
|
|
};
|
|
|
|
|
|
|
|
TLSSocket.prototype.setServername = function(name) {
|
2018-08-03 00:51:02 +02:00
|
|
|
validateString(name, 'name');
|
2018-01-10 20:33:49 +01:00
|
|
|
|
|
|
|
if (this._tlsOptions.isServer) {
|
2018-03-04 22:16:24 +01:00
|
|
|
throw new ERR_TLS_SNI_FROM_SERVER();
|
2018-01-10 20:33:49 +01:00
|
|
|
}
|
|
|
|
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
this._handle.setServername(name);
|
2013-06-13 15:36:00 +02:00
|
|
|
};
|
|
|
|
|
|
|
|
TLSSocket.prototype.setSession = function(session) {
|
2015-01-29 02:05:53 +01:00
|
|
|
if (typeof session === 'string')
|
2016-06-02 18:55:36 +02:00
|
|
|
session = Buffer.from(session, 'latin1');
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
this._handle.setSession(session);
|
2013-06-13 15:36:00 +02:00
|
|
|
};
|
|
|
|
|
2014-04-17 13:57:36 +02:00
|
|
|
TLSSocket.prototype.getPeerCertificate = function(detailed) {
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
if (this._handle) {
|
2014-04-17 13:57:36 +02:00
|
|
|
return common.translatePeerCertificate(
|
2018-11-08 22:40:46 +01:00
|
|
|
this._handle.getPeerCertificate(detailed)) || {};
|
|
|
|
}
|
|
|
|
|
|
|
|
return null;
|
|
|
|
};
|
|
|
|
|
|
|
|
TLSSocket.prototype.getCertificate = function() {
|
|
|
|
if (this._handle) {
|
|
|
|
// It's not a peer cert, but the formatting is identical.
|
|
|
|
return common.translatePeerCertificate(
|
|
|
|
this._handle.getCertificate()) || {};
|
2014-04-17 13:57:36 +02:00
|
|
|
}
|
2013-06-13 15:36:00 +02:00
|
|
|
|
|
|
|
return null;
|
|
|
|
};
|
|
|
|
|
2018-08-05 22:20:02 +02:00
|
|
|
// Proxy TLSSocket handle methods
|
|
|
|
function makeSocketMethodProxy(name) {
|
|
|
|
return function socketMethodProxy(...args) {
|
|
|
|
if (this._handle)
|
|
|
|
return this._handle[name].apply(this._handle, args);
|
2013-06-13 15:36:00 +02:00
|
|
|
return null;
|
2018-08-05 22:20:02 +02:00
|
|
|
};
|
|
|
|
}
|
2015-05-22 11:20:26 +02:00
|
|
|
|
2018-08-05 22:20:02 +02:00
|
|
|
[
|
2019-03-12 20:09:24 +01:00
|
|
|
'getCipher',
|
|
|
|
'getEphemeralKeyInfo',
|
|
|
|
'getFinished',
|
|
|
|
'getPeerFinished',
|
|
|
|
'getProtocol',
|
|
|
|
'getSession',
|
|
|
|
'getTLSTicket',
|
|
|
|
'isSessionReused',
|
2018-08-05 22:20:02 +02:00
|
|
|
].forEach((method) => {
|
|
|
|
TLSSocket.prototype[method] = makeSocketMethodProxy(method);
|
|
|
|
});
|
2015-05-22 11:20:26 +02:00
|
|
|
|
2013-06-13 15:36:00 +02:00
|
|
|
// TODO: support anonymous (nocert) and PSK
|
|
|
|
|
|
|
|
|
2019-01-31 23:41:10 +01:00
|
|
|
function onServerSocketSecure() {
|
2017-09-23 20:18:28 +02:00
|
|
|
if (this._requestCert) {
|
|
|
|
const verifyError = this._handle.verifyError();
|
|
|
|
if (verifyError) {
|
|
|
|
this.authorizationError = verifyError.code;
|
|
|
|
|
|
|
|
if (this._rejectUnauthorized)
|
|
|
|
this.destroy();
|
|
|
|
} else {
|
|
|
|
this.authorized = true;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
if (!this.destroyed && this._releaseControl()) {
|
|
|
|
debug('server emit secureConnection');
|
2017-09-23 20:18:28 +02:00
|
|
|
this._tlsOptions.server.emit('secureConnection', this);
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
}
|
2017-09-23 20:18:28 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
function onSocketTLSError(err) {
|
|
|
|
if (!this._controlReleased && !this[kErrorEmitted]) {
|
|
|
|
this[kErrorEmitted] = true;
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('server emit tlsClientError:', err);
|
2017-09-23 20:18:28 +02:00
|
|
|
this._tlsOptions.server.emit('tlsClientError', err, this);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
function onSocketClose(err) {
|
|
|
|
// Closed because of error - no need to emit it twice
|
|
|
|
if (err)
|
|
|
|
return;
|
|
|
|
|
|
|
|
// Emit ECONNRESET
|
|
|
|
if (!this._controlReleased && !this[kErrorEmitted]) {
|
|
|
|
this[kErrorEmitted] = true;
|
2018-03-15 14:22:43 +01:00
|
|
|
// eslint-disable-next-line no-restricted-syntax
|
2017-09-23 20:18:28 +02:00
|
|
|
const connReset = new Error('socket hang up');
|
|
|
|
connReset.code = 'ECONNRESET';
|
|
|
|
this._tlsOptions.server.emit('tlsClientError', connReset, this);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
function tlsConnectionListener(rawSocket) {
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('net.Server.on(connection): new TLSSocket');
|
2017-09-23 20:18:28 +02:00
|
|
|
const socket = new TLSSocket(rawSocket, {
|
|
|
|
secureContext: this._sharedCreds,
|
|
|
|
isServer: true,
|
|
|
|
server: this,
|
|
|
|
requestCert: this.requestCert,
|
|
|
|
rejectUnauthorized: this.rejectUnauthorized,
|
|
|
|
handshakeTimeout: this[kHandshakeTimeout],
|
|
|
|
ALPNProtocols: this.ALPNProtocols,
|
|
|
|
SNICallback: this[kSNICallback] || SNICallback
|
|
|
|
});
|
|
|
|
|
2019-01-31 23:41:10 +01:00
|
|
|
socket.on('secure', onServerSocketSecure);
|
2017-09-23 20:18:28 +02:00
|
|
|
|
|
|
|
socket[kErrorEmitted] = false;
|
|
|
|
socket.on('close', onSocketClose);
|
|
|
|
socket.on('_tlsError', onSocketTLSError);
|
|
|
|
}
|
|
|
|
|
2013-06-13 15:36:00 +02:00
|
|
|
// AUTHENTICATION MODES
|
|
|
|
//
|
|
|
|
// There are several levels of authentication that TLS/SSL supports.
|
|
|
|
// Read more about this in "man SSL_set_verify".
|
|
|
|
//
|
|
|
|
// 1. The server sends a certificate to the client but does not request a
|
|
|
|
// cert from the client. This is common for most HTTPS servers. The browser
|
|
|
|
// can verify the identity of the server, but the server does not know who
|
|
|
|
// the client is. Authenticating the client is usually done over HTTP using
|
|
|
|
// login boxes and cookies and stuff.
|
|
|
|
//
|
|
|
|
// 2. The server sends a cert to the client and requests that the client
|
|
|
|
// also send it a cert. The client knows who the server is and the server is
|
|
|
|
// requesting the client also identify themselves. There are several
|
|
|
|
// outcomes:
|
|
|
|
//
|
|
|
|
// A) verifyError returns null meaning the client's certificate is signed
|
2017-06-17 15:11:45 +02:00
|
|
|
// by one of the server's CAs. The server now knows the client's identity
|
2013-06-13 15:36:00 +02:00
|
|
|
// and the client is authorized.
|
|
|
|
//
|
|
|
|
// B) For some reason the client's certificate is not acceptable -
|
|
|
|
// verifyError returns a string indicating the problem. The server can
|
|
|
|
// either (i) reject the client or (ii) allow the client to connect as an
|
|
|
|
// unauthorized connection.
|
|
|
|
//
|
|
|
|
// The mode is controlled by two boolean variables.
|
|
|
|
//
|
|
|
|
// requestCert
|
|
|
|
// If true the server requests a certificate from client connections. For
|
|
|
|
// the common HTTPS case, users will want this to be false, which is what
|
|
|
|
// it defaults to.
|
|
|
|
//
|
|
|
|
// rejectUnauthorized
|
|
|
|
// If true clients whose certificates are invalid for any reason will not
|
|
|
|
// be allowed to make connections. If false, they will simply be marked as
|
|
|
|
// unauthorized but secure communication will continue. By default this is
|
|
|
|
// true.
|
|
|
|
//
|
|
|
|
//
|
|
|
|
//
|
|
|
|
// Options:
|
|
|
|
// - requestCert. Send verify request. Default to false.
|
|
|
|
// - rejectUnauthorized. Boolean, default to true.
|
|
|
|
// - key. string.
|
|
|
|
// - cert: string.
|
2016-04-15 16:49:36 +02:00
|
|
|
// - clientCertEngine: string.
|
2013-06-13 15:36:00 +02:00
|
|
|
// - ca: string or array of strings.
|
|
|
|
// - sessionTimeout: integer.
|
|
|
|
//
|
|
|
|
// emit 'secureConnection'
|
|
|
|
// function (tlsSocket) { }
|
|
|
|
//
|
|
|
|
// "UNABLE_TO_GET_ISSUER_CERT", "UNABLE_TO_GET_CRL",
|
|
|
|
// "UNABLE_TO_DECRYPT_CERT_SIGNATURE", "UNABLE_TO_DECRYPT_CRL_SIGNATURE",
|
|
|
|
// "UNABLE_TO_DECODE_ISSUER_PUBLIC_KEY", "CERT_SIGNATURE_FAILURE",
|
|
|
|
// "CRL_SIGNATURE_FAILURE", "CERT_NOT_YET_VALID" "CERT_HAS_EXPIRED",
|
|
|
|
// "CRL_NOT_YET_VALID", "CRL_HAS_EXPIRED" "ERROR_IN_CERT_NOT_BEFORE_FIELD",
|
|
|
|
// "ERROR_IN_CERT_NOT_AFTER_FIELD", "ERROR_IN_CRL_LAST_UPDATE_FIELD",
|
|
|
|
// "ERROR_IN_CRL_NEXT_UPDATE_FIELD", "OUT_OF_MEM",
|
|
|
|
// "DEPTH_ZERO_SELF_SIGNED_CERT", "SELF_SIGNED_CERT_IN_CHAIN",
|
|
|
|
// "UNABLE_TO_GET_ISSUER_CERT_LOCALLY", "UNABLE_TO_VERIFY_LEAF_SIGNATURE",
|
|
|
|
// "CERT_CHAIN_TOO_LONG", "CERT_REVOKED" "INVALID_CA",
|
|
|
|
// "PATH_LENGTH_EXCEEDED", "INVALID_PURPOSE" "CERT_UNTRUSTED",
|
|
|
|
// "CERT_REJECTED"
|
|
|
|
//
|
2016-11-21 22:50:02 +01:00
|
|
|
function Server(options, listener) {
|
|
|
|
if (!(this instanceof Server))
|
|
|
|
return new Server(options, listener);
|
2015-01-29 02:05:53 +01:00
|
|
|
|
2016-11-21 22:50:02 +01:00
|
|
|
if (typeof options === 'function') {
|
|
|
|
listener = options;
|
2013-06-13 15:36:00 +02:00
|
|
|
options = {};
|
2016-11-21 22:50:02 +01:00
|
|
|
} else if (options == null || typeof options === 'object') {
|
|
|
|
options = options || {};
|
|
|
|
} else {
|
2018-03-19 13:33:46 +01:00
|
|
|
throw new ERR_INVALID_ARG_TYPE('options', 'Object', options);
|
2013-06-13 15:36:00 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
this._contexts = [];
|
2018-10-22 21:17:06 +02:00
|
|
|
this.requestCert = options.requestCert === true;
|
|
|
|
this.rejectUnauthorized = options.rejectUnauthorized !== false;
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2018-10-22 21:17:06 +02:00
|
|
|
if (options.sessionTimeout)
|
|
|
|
this.sessionTimeout = options.sessionTimeout;
|
|
|
|
|
|
|
|
if (options.ticketKeys)
|
|
|
|
this.ticketKeys = options.ticketKeys;
|
|
|
|
|
|
|
|
if (options.ALPNProtocols)
|
|
|
|
tls.convertALPNProtocols(options.ALPNProtocols, this);
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2018-10-13 20:18:31 +02:00
|
|
|
this.setSecureContext(options);
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
this[kHandshakeTimeout] = options.handshakeTimeout || (120 * 1000);
|
|
|
|
this[kSNICallback] = options.SNICallback;
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
if (typeof this[kHandshakeTimeout] !== 'number') {
|
2018-03-19 14:18:50 +01:00
|
|
|
throw new ERR_INVALID_ARG_TYPE(
|
|
|
|
'options.handshakeTimeout', 'number', options.handshakeTimeout);
|
2013-06-13 15:36:00 +02:00
|
|
|
}
|
|
|
|
|
2018-05-25 22:21:43 +02:00
|
|
|
if (this[kSNICallback] && typeof this[kSNICallback] !== 'function') {
|
|
|
|
throw new ERR_INVALID_ARG_TYPE(
|
|
|
|
'options.SNICallback', 'function', options.SNICallback);
|
|
|
|
}
|
|
|
|
|
2013-06-13 15:36:00 +02:00
|
|
|
// constructor call
|
2017-09-23 20:18:28 +02:00
|
|
|
net.Server.call(this, tlsConnectionListener);
|
2013-06-13 15:36:00 +02:00
|
|
|
|
|
|
|
if (listener) {
|
|
|
|
this.on('secureConnection', listener);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2019-03-18 17:31:43 +01:00
|
|
|
Object.setPrototypeOf(Server.prototype, net.Server.prototype);
|
|
|
|
Object.setPrototypeOf(Server, net.Server);
|
2013-06-13 15:36:00 +02:00
|
|
|
exports.Server = Server;
|
2018-07-11 12:36:36 +02:00
|
|
|
exports.createServer = function createServer(options, listener) {
|
2013-06-13 15:36:00 +02:00
|
|
|
return new Server(options, listener);
|
|
|
|
};
|
|
|
|
|
|
|
|
|
2018-10-13 20:18:31 +02:00
|
|
|
Server.prototype.setSecureContext = function(options) {
|
|
|
|
if (options === null || typeof options !== 'object')
|
|
|
|
throw new ERR_INVALID_ARG_TYPE('options', 'Object', options);
|
|
|
|
|
|
|
|
if (options.pfx)
|
|
|
|
this.pfx = options.pfx;
|
|
|
|
else
|
|
|
|
this.pfx = undefined;
|
|
|
|
|
|
|
|
if (options.key)
|
|
|
|
this.key = options.key;
|
|
|
|
else
|
|
|
|
this.key = undefined;
|
|
|
|
|
|
|
|
if (options.passphrase)
|
|
|
|
this.passphrase = options.passphrase;
|
|
|
|
else
|
|
|
|
this.passphrase = undefined;
|
|
|
|
|
|
|
|
if (options.cert)
|
|
|
|
this.cert = options.cert;
|
|
|
|
else
|
|
|
|
this.cert = undefined;
|
|
|
|
|
|
|
|
if (options.clientCertEngine)
|
|
|
|
this.clientCertEngine = options.clientCertEngine;
|
|
|
|
else
|
|
|
|
this.clientCertEngine = undefined;
|
|
|
|
|
|
|
|
if (options.ca)
|
|
|
|
this.ca = options.ca;
|
|
|
|
else
|
|
|
|
this.ca = undefined;
|
|
|
|
|
2018-05-06 06:52:34 +02:00
|
|
|
if (options.minVersion)
|
|
|
|
this.minVersion = options.minVersion;
|
|
|
|
else
|
|
|
|
this.minVersion = undefined;
|
|
|
|
|
|
|
|
if (options.maxVersion)
|
|
|
|
this.maxVersion = options.maxVersion;
|
|
|
|
else
|
|
|
|
this.maxVersion = undefined;
|
|
|
|
|
2018-10-13 20:18:31 +02:00
|
|
|
if (options.secureProtocol)
|
|
|
|
this.secureProtocol = options.secureProtocol;
|
|
|
|
else
|
|
|
|
this.secureProtocol = undefined;
|
|
|
|
|
|
|
|
if (options.crl)
|
|
|
|
this.crl = options.crl;
|
|
|
|
else
|
|
|
|
this.crl = undefined;
|
|
|
|
|
|
|
|
if (options.ciphers)
|
|
|
|
this.ciphers = options.ciphers;
|
|
|
|
else
|
|
|
|
this.ciphers = undefined;
|
|
|
|
|
|
|
|
if (options.ecdhCurve !== undefined)
|
|
|
|
this.ecdhCurve = options.ecdhCurve;
|
|
|
|
else
|
|
|
|
this.ecdhCurve = undefined;
|
|
|
|
|
|
|
|
if (options.dhparam)
|
|
|
|
this.dhparam = options.dhparam;
|
|
|
|
else
|
|
|
|
this.dhparam = undefined;
|
|
|
|
|
|
|
|
if (options.honorCipherOrder !== undefined)
|
|
|
|
this.honorCipherOrder = !!options.honorCipherOrder;
|
|
|
|
else
|
|
|
|
this.honorCipherOrder = true;
|
|
|
|
|
|
|
|
const secureOptions = options.secureOptions || 0;
|
|
|
|
|
|
|
|
if (secureOptions)
|
|
|
|
this.secureOptions = secureOptions;
|
|
|
|
else
|
|
|
|
this.secureOptions = undefined;
|
|
|
|
|
|
|
|
if (options.sessionIdContext) {
|
|
|
|
this.sessionIdContext = options.sessionIdContext;
|
|
|
|
} else {
|
|
|
|
this.sessionIdContext = crypto.createHash('sha1')
|
|
|
|
.update(process.argv.join(' '))
|
|
|
|
.digest('hex')
|
|
|
|
.slice(0, 32);
|
|
|
|
}
|
|
|
|
|
|
|
|
this._sharedCreds = tls.createSecureContext({
|
|
|
|
pfx: this.pfx,
|
|
|
|
key: this.key,
|
|
|
|
passphrase: this.passphrase,
|
|
|
|
cert: this.cert,
|
|
|
|
clientCertEngine: this.clientCertEngine,
|
|
|
|
ca: this.ca,
|
|
|
|
ciphers: this.ciphers,
|
|
|
|
ecdhCurve: this.ecdhCurve,
|
|
|
|
dhparam: this.dhparam,
|
2018-05-06 06:52:34 +02:00
|
|
|
minVersion: this.minVersion,
|
|
|
|
maxVersion: this.maxVersion,
|
2018-10-13 20:18:31 +02:00
|
|
|
secureProtocol: this.secureProtocol,
|
|
|
|
secureOptions: this.secureOptions,
|
|
|
|
honorCipherOrder: this.honorCipherOrder,
|
|
|
|
crl: this.crl,
|
|
|
|
sessionIdContext: this.sessionIdContext
|
|
|
|
});
|
|
|
|
|
|
|
|
if (this.sessionTimeout)
|
|
|
|
this._sharedCreds.context.setSessionTimeout(this.sessionTimeout);
|
|
|
|
|
|
|
|
if (options.ticketKeys) {
|
|
|
|
this.ticketKeys = options.ticketKeys;
|
|
|
|
this.setTicketKeys(this.ticketKeys);
|
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
|
2013-07-21 05:11:02 +02:00
|
|
|
Server.prototype._getServerData = function() {
|
|
|
|
return {
|
2015-07-22 22:52:23 +02:00
|
|
|
ticketKeys: this.getTicketKeys().toString('hex')
|
2013-07-21 05:11:02 +02:00
|
|
|
};
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
Server.prototype._setServerData = function(data) {
|
2016-01-26 00:00:06 +01:00
|
|
|
this.setTicketKeys(Buffer.from(data.ticketKeys, 'hex'));
|
2015-07-22 22:52:23 +02:00
|
|
|
};
|
|
|
|
|
|
|
|
|
2019-01-16 20:12:30 +01:00
|
|
|
Server.prototype.getTicketKeys = function getTicketKeys() {
|
|
|
|
return this._sharedCreds.context.getTicketKeys();
|
2015-07-22 22:52:23 +02:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
Server.prototype.setTicketKeys = function setTicketKeys(keys) {
|
|
|
|
this._sharedCreds.context.setTicketKeys(keys);
|
2013-07-21 05:11:02 +02:00
|
|
|
};
|
|
|
|
|
|
|
|
|
2019-03-18 17:31:43 +01:00
|
|
|
Server.prototype.setOptions = deprecate(function(options) {
|
2016-03-27 15:09:08 +02:00
|
|
|
this.requestCert = options.requestCert === true;
|
|
|
|
this.rejectUnauthorized = options.rejectUnauthorized !== false;
|
2013-06-13 15:36:00 +02:00
|
|
|
|
|
|
|
if (options.pfx) this.pfx = options.pfx;
|
|
|
|
if (options.key) this.key = options.key;
|
|
|
|
if (options.passphrase) this.passphrase = options.passphrase;
|
|
|
|
if (options.cert) this.cert = options.cert;
|
2016-04-15 16:49:36 +02:00
|
|
|
if (options.clientCertEngine)
|
|
|
|
this.clientCertEngine = options.clientCertEngine;
|
2013-06-13 15:36:00 +02:00
|
|
|
if (options.ca) this.ca = options.ca;
|
2018-05-06 06:52:34 +02:00
|
|
|
if (options.minVersion) this.minVersion = options.minVersion;
|
|
|
|
if (options.maxVersion) this.maxVersion = options.maxVersion;
|
2013-06-13 15:36:00 +02:00
|
|
|
if (options.secureProtocol) this.secureProtocol = options.secureProtocol;
|
|
|
|
if (options.crl) this.crl = options.crl;
|
|
|
|
if (options.ciphers) this.ciphers = options.ciphers;
|
2015-01-29 02:05:53 +01:00
|
|
|
if (options.ecdhCurve !== undefined)
|
2013-10-14 16:53:59 +02:00
|
|
|
this.ecdhCurve = options.ecdhCurve;
|
2014-08-27 11:00:13 +02:00
|
|
|
if (options.dhparam) this.dhparam = options.dhparam;
|
2013-06-13 15:36:00 +02:00
|
|
|
if (options.sessionTimeout) this.sessionTimeout = options.sessionTimeout;
|
2014-02-03 22:32:13 +01:00
|
|
|
if (options.ticketKeys) this.ticketKeys = options.ticketKeys;
|
2013-06-13 15:36:00 +02:00
|
|
|
var secureOptions = options.secureOptions || 0;
|
2015-02-15 18:43:36 +01:00
|
|
|
if (options.honorCipherOrder !== undefined)
|
|
|
|
this.honorCipherOrder = !!options.honorCipherOrder;
|
2014-06-25 12:47:59 +02:00
|
|
|
else
|
2015-02-15 18:43:36 +01:00
|
|
|
this.honorCipherOrder = true;
|
2013-06-13 15:36:00 +02:00
|
|
|
if (secureOptions) this.secureOptions = secureOptions;
|
2015-04-23 08:25:15 +02:00
|
|
|
if (options.ALPNProtocols)
|
|
|
|
tls.convertALPNProtocols(options.ALPNProtocols, this);
|
2013-06-13 15:36:00 +02:00
|
|
|
if (options.sessionIdContext) {
|
|
|
|
this.sessionIdContext = options.sessionIdContext;
|
2013-08-23 15:53:16 +02:00
|
|
|
} else {
|
2015-11-10 00:19:11 +01:00
|
|
|
this.sessionIdContext = crypto.createHash('sha1')
|
|
|
|
.update(process.argv.join(' '))
|
|
|
|
.digest('hex')
|
|
|
|
.slice(0, 32);
|
2013-06-13 15:36:00 +02:00
|
|
|
}
|
2018-10-22 21:17:06 +02:00
|
|
|
}, 'Server.prototype.setOptions() is deprecated', 'DEP0122');
|
2013-06-13 15:36:00 +02:00
|
|
|
|
|
|
|
// SNI Contexts High-Level API
|
2014-03-07 00:27:01 +01:00
|
|
|
Server.prototype.addContext = function(servername, context) {
|
2013-06-13 15:36:00 +02:00
|
|
|
if (!servername) {
|
2018-03-04 22:16:24 +01:00
|
|
|
throw new ERR_TLS_REQUIRED_SERVER_NAME();
|
2013-06-13 15:36:00 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
var re = new RegExp('^' +
|
2016-11-03 19:32:06 +01:00
|
|
|
servername.replace(/([.^$+?\-\\[\]{}])/g, '\\$1')
|
2016-09-18 07:43:49 +02:00
|
|
|
.replace(/\*/g, '[^.]*') +
|
2013-06-13 15:36:00 +02:00
|
|
|
'$');
|
2014-03-07 00:27:01 +01:00
|
|
|
this._contexts.push([re, tls.createSecureContext(context).context]);
|
2013-06-13 15:36:00 +02:00
|
|
|
};
|
|
|
|
|
2013-08-03 19:29:54 +02:00
|
|
|
function SNICallback(servername, callback) {
|
2017-09-23 20:18:28 +02:00
|
|
|
const contexts = this.server._contexts;
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
for (var i = 0; i < contexts.length; i++) {
|
|
|
|
const elem = contexts[i];
|
2017-06-08 01:00:33 +02:00
|
|
|
if (elem[0].test(servername)) {
|
2017-09-23 20:18:28 +02:00
|
|
|
callback(null, elem[1]);
|
|
|
|
return;
|
2013-06-13 15:36:00 +02:00
|
|
|
}
|
2017-09-23 20:18:28 +02:00
|
|
|
}
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
callback(null, undefined);
|
2013-08-02 18:11:17 +02:00
|
|
|
}
|
|
|
|
|
2013-06-13 15:36:00 +02:00
|
|
|
|
|
|
|
// Target API:
|
|
|
|
//
|
|
|
|
// var s = tls.connect({port: 8000, host: "google.com"}, function() {
|
|
|
|
// if (!s.authorized) {
|
|
|
|
// s.destroy();
|
|
|
|
// return;
|
|
|
|
// }
|
|
|
|
//
|
|
|
|
// // s.socket;
|
|
|
|
//
|
|
|
|
// s.end("hello world\n");
|
|
|
|
// });
|
|
|
|
//
|
|
|
|
//
|
|
|
|
function normalizeConnectArgs(listArgs) {
|
2018-12-18 03:15:57 +01:00
|
|
|
const args = net._normalizeArgs(listArgs);
|
|
|
|
const options = args[0];
|
|
|
|
const cb = args[1];
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2016-11-18 20:37:32 +01:00
|
|
|
// If args[0] was options, then normalize dealt with it.
|
2017-06-17 15:11:45 +02:00
|
|
|
// If args[0] is port, or args[0], args[1] is host, port, we need to
|
2016-11-18 20:37:32 +01:00
|
|
|
// find the options and merge them in, normalize's options has only
|
|
|
|
// the host/port/path args that it knows about, not the tls options.
|
|
|
|
// This means that options.host overrides a host arg.
|
2015-01-29 02:05:53 +01:00
|
|
|
if (listArgs[1] !== null && typeof listArgs[1] === 'object') {
|
2018-12-18 03:15:57 +01:00
|
|
|
Object.assign(options, listArgs[1]);
|
2015-01-29 02:05:53 +01:00
|
|
|
} else if (listArgs[2] !== null && typeof listArgs[2] === 'object') {
|
2018-12-18 03:15:57 +01:00
|
|
|
Object.assign(options, listArgs[2]);
|
2013-06-13 15:36:00 +02:00
|
|
|
}
|
|
|
|
|
2018-12-18 03:15:57 +01:00
|
|
|
return cb ? [options, cb] : [options];
|
2013-06-13 15:36:00 +02:00
|
|
|
}
|
|
|
|
|
2017-09-23 20:18:28 +02:00
|
|
|
function onConnectSecure() {
|
|
|
|
const options = this[kConnectOptions];
|
|
|
|
|
|
|
|
// Check the size of DHE parameter above minimum requirement
|
|
|
|
// specified in options.
|
|
|
|
const ekeyinfo = this.getEphemeralKeyInfo();
|
|
|
|
if (ekeyinfo.type === 'DH' && ekeyinfo.size < options.minDHSize) {
|
2018-03-04 22:16:24 +01:00
|
|
|
const err = new ERR_TLS_DH_PARAM_SIZE(ekeyinfo.size);
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('client emit:', err);
|
2017-09-23 20:18:28 +02:00
|
|
|
this.emit('error', err);
|
|
|
|
this.destroy();
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
let verifyError = this._handle.verifyError();
|
|
|
|
|
|
|
|
// Verify that server's identity matches it's certificate's names
|
|
|
|
// Unless server has resumed our existing session
|
|
|
|
if (!verifyError && !this.isSessionReused()) {
|
|
|
|
const hostname = options.servername ||
|
|
|
|
options.host ||
|
|
|
|
(options.socket && options.socket._host) ||
|
|
|
|
'localhost';
|
2017-12-15 00:45:44 +01:00
|
|
|
const cert = this.getPeerCertificate(true);
|
2017-09-23 20:18:28 +02:00
|
|
|
verifyError = options.checkServerIdentity(hostname, cert);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (verifyError) {
|
|
|
|
this.authorized = false;
|
|
|
|
this.authorizationError = verifyError.code || verifyError.message;
|
|
|
|
|
|
|
|
if (options.rejectUnauthorized) {
|
|
|
|
this.destroy(verifyError);
|
|
|
|
return;
|
|
|
|
} else {
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('client emit secureConnect');
|
2017-09-23 20:18:28 +02:00
|
|
|
this.emit('secureConnect');
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
this.authorized = true;
|
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>
2018-11-29 02:58:08 +01:00
|
|
|
debug('client emit secureConnect');
|
2017-09-23 20:18:28 +02:00
|
|
|
this.emit('secureConnect');
|
|
|
|
}
|
|
|
|
|
|
|
|
this.removeListener('end', onConnectEnd);
|
|
|
|
}
|
|
|
|
|
|
|
|
function onConnectEnd() {
|
|
|
|
// NOTE: This logic is shared with _http_client.js
|
|
|
|
if (!this._hadError) {
|
|
|
|
const options = this[kConnectOptions];
|
|
|
|
this._hadError = true;
|
2018-03-15 14:22:43 +01:00
|
|
|
// eslint-disable-next-line no-restricted-syntax
|
2018-02-25 21:43:23 +01:00
|
|
|
const error = new Error('Client network socket disconnected before ' +
|
|
|
|
'secure TLS connection was established');
|
2017-09-23 20:18:28 +02:00
|
|
|
error.code = 'ECONNRESET';
|
|
|
|
error.path = options.path;
|
|
|
|
error.host = options.host;
|
|
|
|
error.port = options.port;
|
|
|
|
error.localAddress = options.localAddress;
|
|
|
|
this.destroy(error);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-07-20 04:02:44 +02:00
|
|
|
let warnOnAllowUnauthorized = true;
|
|
|
|
|
2018-07-11 12:36:36 +02:00
|
|
|
// Arguments: [port,] [host,] [options,] [cb]
|
|
|
|
exports.connect = function connect(...args) {
|
2015-12-20 08:01:34 +01:00
|
|
|
args = normalizeConnectArgs(args);
|
2013-06-13 15:36:00 +02:00
|
|
|
var options = args[0];
|
|
|
|
var cb = args[1];
|
2018-07-20 04:02:44 +02:00
|
|
|
const allowUnauthorized = process.env.NODE_TLS_REJECT_UNAUTHORIZED === '0';
|
|
|
|
|
|
|
|
if (allowUnauthorized && warnOnAllowUnauthorized) {
|
|
|
|
warnOnAllowUnauthorized = false;
|
|
|
|
process.emitWarning('Setting the NODE_TLS_REJECT_UNAUTHORIZED ' +
|
|
|
|
'environment variable to \'0\' makes TLS connections ' +
|
|
|
|
'and HTTPS requests insecure by disabling ' +
|
|
|
|
'certificate verification.');
|
|
|
|
}
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2018-12-18 03:15:57 +01:00
|
|
|
options = {
|
2018-07-20 04:02:44 +02:00
|
|
|
rejectUnauthorized: !allowUnauthorized,
|
2014-09-05 16:56:55 +02:00
|
|
|
ciphers: tls.DEFAULT_CIPHERS,
|
2015-05-22 11:21:54 +02:00
|
|
|
checkServerIdentity: tls.checkServerIdentity,
|
2018-12-18 03:15:57 +01:00
|
|
|
minDHSize: 1024,
|
|
|
|
...options
|
2013-06-13 15:36:00 +02:00
|
|
|
};
|
2014-09-05 16:56:55 +02:00
|
|
|
|
2015-04-26 14:19:38 +02:00
|
|
|
if (!options.keepAlive)
|
|
|
|
options.singleUse = true;
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2014-09-05 16:56:55 +02:00
|
|
|
assert(typeof options.checkServerIdentity === 'function');
|
2015-05-22 11:21:54 +02:00
|
|
|
assert(typeof options.minDHSize === 'number',
|
|
|
|
'options.minDHSize is not a number: ' + options.minDHSize);
|
|
|
|
assert(options.minDHSize > 0,
|
2015-11-02 13:14:14 +01:00
|
|
|
'options.minDHSize is not a positive number: ' +
|
2015-05-22 11:21:54 +02:00
|
|
|
options.minDHSize);
|
2014-09-05 16:56:55 +02:00
|
|
|
|
2016-01-12 22:04:50 +01:00
|
|
|
const context = options.secureContext || tls.createSecureContext(options);
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2018-12-19 23:42:58 +01:00
|
|
|
var tlssock = new TLSSocket(options.socket, {
|
2017-08-01 08:58:39 +02:00
|
|
|
pipe: !!options.path,
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
secureContext: context,
|
|
|
|
isServer: false,
|
|
|
|
requestCert: true,
|
2016-03-27 15:09:08 +02:00
|
|
|
rejectUnauthorized: options.rejectUnauthorized !== false,
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
session: options.session,
|
2017-10-31 21:03:28 +01:00
|
|
|
ALPNProtocols: options.ALPNProtocols,
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
requestOCSP: options.requestOCSP
|
|
|
|
});
|
2013-09-24 14:53:49 +02:00
|
|
|
|
2018-12-19 23:42:58 +01:00
|
|
|
tlssock[kConnectOptions] = options;
|
2017-09-23 20:18:28 +02:00
|
|
|
|
2013-09-24 14:53:49 +02:00
|
|
|
if (cb)
|
2018-12-19 23:42:58 +01:00
|
|
|
tlssock.once('secureConnect', cb);
|
2013-09-24 14:53:49 +02:00
|
|
|
|
|
|
|
if (!options.socket) {
|
2018-12-19 23:42:58 +01:00
|
|
|
// If user provided the socket, its their responsibility to manage its
|
|
|
|
// connectivity. If we created one internally, we connect it.
|
2017-08-01 08:58:39 +02:00
|
|
|
const connectOpt = {
|
|
|
|
path: options.path,
|
|
|
|
port: options.port,
|
|
|
|
host: options.host,
|
|
|
|
family: options.family,
|
|
|
|
localAddress: options.localAddress,
|
2018-11-21 16:12:17 +01:00
|
|
|
localPort: options.localPort,
|
2017-08-01 08:58:39 +02:00
|
|
|
lookup: options.lookup
|
|
|
|
};
|
2019-01-15 16:12:12 +01:00
|
|
|
|
|
|
|
if (options.timeout) {
|
|
|
|
tlssock.setTimeout(options.timeout);
|
|
|
|
}
|
|
|
|
|
2018-12-19 23:42:58 +01:00
|
|
|
tlssock.connect(connectOpt, tlssock._start);
|
2013-09-24 14:53:49 +02:00
|
|
|
}
|
|
|
|
|
2018-12-19 23:42:58 +01:00
|
|
|
tlssock._releaseControl();
|
2013-06-13 15:36:00 +02:00
|
|
|
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
if (options.session)
|
2018-12-19 23:42:58 +01:00
|
|
|
tlssock.setSession(options.session);
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2018-01-13 00:36:21 +01:00
|
|
|
if (options.servername) {
|
|
|
|
if (!ipServernameWarned && net.isIP(options.servername)) {
|
|
|
|
process.emitWarning(
|
|
|
|
'Setting the TLS ServerName to an IP address is not permitted by ' +
|
|
|
|
'RFC 6066. This will be ignored in a future version.',
|
|
|
|
'DeprecationWarning',
|
|
|
|
'DEP0123'
|
|
|
|
);
|
|
|
|
ipServernameWarned = true;
|
|
|
|
}
|
2018-12-19 23:42:58 +01:00
|
|
|
tlssock.setServername(options.servername);
|
2018-01-13 00:36:21 +01:00
|
|
|
}
|
2013-06-13 15:36:00 +02:00
|
|
|
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
if (options.socket)
|
2018-12-19 23:42:58 +01:00
|
|
|
tlssock._start();
|
2013-06-13 15:36:00 +02:00
|
|
|
|
2018-12-19 23:42:58 +01:00
|
|
|
tlssock.on('secure', onConnectSecure);
|
|
|
|
tlssock.once('end', onConnectEnd);
|
stream_base: introduce StreamBase
StreamBase is an improved way to write C++ streams. The class itself is
for separting `StreamWrap` (with the methods like `.writeAsciiString`,
`.writeBuffer`, `.writev`, etc) from the `HandleWrap` class, making
possible to write abstract C++ streams that are not bound to any uv
socket.
The following methods are important part of the abstraction (which
mimics libuv's stream API):
* Events:
* `OnAlloc(size_t size, uv_buf_t*)`
* `OnRead(ssize_t nread, const uv_buf_t*, uv_handle_type pending)`
* `OnAfterWrite(WriteWrap*)`
* Wrappers:
* `DoShutdown(ShutdownWrap*)`
* `DoTryWrite(uv_buf_t** bufs, size_t* count)`
* `DoWrite(WriteWrap*, uv_buf_t*, size_t count, uv_stream_t* handle)`
* `Error()`
* `ClearError()`
The implementation should provide all of these methods, thus providing
the access to the underlying resource (be it uv handle, TLS socket, or
anything else).
A C++ stream may consume the input of another stream by replacing the
event callbacks and proxying the writes. This kind of API is actually
used now for the TLSWrap implementation, making it possible to wrap TLS
stream into another TLS stream. Thus legacy API calls are no longer
required in `_tls_wrap.js`.
PR-URL: https://github.com/iojs/io.js/pull/840
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
2015-02-22 19:59:07 +01:00
|
|
|
|
2018-12-19 23:42:58 +01:00
|
|
|
return tlssock;
|
2013-06-13 15:36:00 +02:00
|
|
|
};
|