-
Notifications
You must be signed in to change notification settings - Fork 18k
crypto/tls: Dial to TLS endpoint requiring ClientAuth does not error #33368
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Same on Linux. What version of Go are you using (go version)?
What operating system and processor architecture are you using (go env)?go env Output
Output
|
This is a consequence of how TLS 1.3 was designed, see: https://golang.org/doc/go1.12#tls_1_3.
|
Indeed, this is unfortunate, but a core property of TLS 1.3 which is necessary for its performance improvements. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Error behaviour has changed on the latest 1.13 beta.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
When connecting to a TLS endpoint that requires a client certificate and the client does not provide one, the
tls.Dial()
succeeds, but the socket read fails - this differs to previous releases.What did you expect to see?
In 1.12.7 the
tls.Dial()
fails and execution never gets to the socket read:What did you see instead?
In 1.13beta1 the
Dial()
returns a nil error, but reading from the socket returnstls: bad certificate
instead:Not a big problem, but tripped our CI tests expecting the dial to fail.
The text was updated successfully, but these errors were encountered: