Rank, 14 days: 7 on the Bun sheet
1 person reported

All time, since Nov 7.

No TLS alert on rejection

“When a TLS client rejects the server's certificate, it must send a fatal alert before closing.”

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/26601/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

TLS client sends no alert when rejecting server certificate. tlsClientError reports a bare ECONNRESET when the Bun client does not trust the CA or the hostname does not match.

Is this your bug?

File my report
Where
node:tls client
Versions
1.4.4. Still reported on the newest version, 1.4.4.
Platforms
macOS
How bad
Breaks a normal workflow.

Not quite your bug?

  1. TLS client sends Finished and certificate before rejecting server2 people
  2. checkServerIdentity never called3 people

Original reports2, newest first

  1. tlsClientError reports Bun-client certificate rejection as a bare ECONNRESET, hiding the alert#48080
  2. Bun's TLS client sends no alert when it rejects the server certificate#48079

Do you work on Bun?

Claim its RAP Sheet to see what your users report and answer them in one place.