Carlos Vinicius e204ae8ce5 tls: propagate singleUse to the secure context ...

tls.connect() sets options.singleUse, and both TLSWrap.prototype.close()
and TLSSocket.prototype._destroySSL() check _secureContext.singleUse
before closing the context. Nothing ever assigned the flag to the
context, so the check never fired and each connection's SSL_CTX stayed
alive until the JS wrapper was garbage collected. The assignment was
lost when the context configuration was extracted into
configSecureContext().

Restore it in createSecureContext(), which owns the JS wrapper the flag
is read from, and make the close idempotent: a socket that swaps its
handle, as autoSelectFamily retries do, shares a single context between
the successive TLSWraps and each of them reaches the same teardown.

Signed-off-by: Carlos Vinicius <viniciusdev.26@gmail.com>
PR-URL: https://github.com/nodejs/node/pull/66025
Fixes: https://github.com/nodejs/node/issues/66002
Refs: https://github.com/nodejs/node/pull/38116
Reviewed-By: Xuguang Mei <meixuguang@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Tim Perry <pimterry@gmail.com>

2026-09-17 03:59:38 +00:00

..

common.js

tls: propagate singleUse to the secure context

2026-09-17 03:59:38 +00:00

secure-context.js

lib: use validateArray for array arguments

2026-08-09 11:55:05 +00:00

wrap.js

tls: propagate singleUse to the secure context

2026-09-17 03:59:38 +00:00