tls: fix authorized state on no-cert TLS1.3 client cert resumption · nodejs/node@15da4a1 · GitHub
Skip to content

Commit 15da4a1

Browse files
pimterryaduh95
authored andcommitted
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: #64677 Reviewed-By: James M Snell <jasnell@gmail.com>
1 parent ca88587 commit 15da4a1

2 files changed

Lines changed: 206 additions & 0 deletions

File tree

lib/internal/tls/wrap.js

Lines changed: 7 additions & 0 deletions
Lines changed: 199 additions & 0 deletions

0 commit comments

Comments
 (0)