Tim Perry c59cd6b046 tls: fix authorized state on no-cert TLS1.3 client cert resumption ...

Previously if you used TLS 1.3 and the server requested a client cert,
but the client didn't send one, and you used rejectUnauthorized:false
the resumed session would report authorized=true. This doesn't match TLS
1.2 behaviour or make any sense, and was purely an artifact of our
internal logic for handling TLS 1.3 resumption details. We now correctly
report the authorization state and/or error from the original connection
in all cases, with a matrix test that fully checks the invariant:
authorized state after resume should always match the initial state.

Signed-off-by: Tim Perry <pimterry@gmail.com>
PR-URL: https://github.com/nodejs/node/pull/64677
Reviewed-By: James M Snell <jasnell@gmail.com>

2026-08-08 15:05:06 +00:00

..

common.js

tls: avoid external memory leak on invalid protocol versions

2025-10-26 16:29:49 +00:00

secure-context.js

crypto,https,tls: runtime-deprecate OpenSSL engine-based APIs (DEP0183)

2026-06-19 18:03:51 +02:00

wrap.js

tls: fix authorized state on no-cert TLS1.3 client cert resumption

2026-08-08 15:05:06 +00:00