2 people reported
All time, since Sep 21.
TLS client sends Finished and certificate before rejecting server
“But its TLS 1.3 Finished is on the wire before the identity check decides.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/bun/issues/4825/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Is this your bug?
File my report- Where
- TLS client
- Versions
- 1.4.3-canary.1
- Platforms
- Linux, macOS
- How bad
- Security risk: something exposed, or done without permission.
Not quite your bug?
- checkServerIdentity never called3 people
- No TLS alert on rejection1 person
Original reports4, newest first
- node:tls: a client that refuses the server still sends its TLS 1.3 client certificate while another TLS socket has unsent data#43999
- fetch: the TLS 1.3 client certificate reaches a server that
checkServerIdentitythen refuses#43998 - node:tls: a client that rejects the server in checkServerIdentity still sends its TLS 1.3 Finished, so the server emits 'secureConnection' where Node emits 'tlsClientError'#43807
- fetch, Bun.SQL (postgres + mysql), Bun.RedisClient and WebSocket send the mTLS client certificate to servers that fail verification#43684