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
crypto/tls: Client-side certificate doesn't work with tip #28925
Comments
Hi @anacrolix - Can you provide us with a reproducible code sample ? It would help us a lot to quickly debug this issue. |
I suspect the author of recent changes to crypto/tls client-side handshakes will be best equipped. I don't have the time at present to isolate any more than I have above. |
/cc @FiloSottile |
No need to isolate it further, but I will need more details to debug this. What's the config? What certificate? Is the server public? If the server is a Go server, what config and version? |
|
Thank you for the extra info! Can you share the address of the server so I can test it? |
You may run it yourself, it's https://github.com/anacrolix/transcoder. I believe you can just do |
Change https://golang.org/cl/151660 mentions this issue: |
This worked, thanks. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
A tls.Config containing a single client-side certificate fails with remote error: unknown certificate on the recent go version. With release (1.11), this doesn't happen. Setting tls max version 1.2 doesn't seem to help. May be related to #28779.
The text was updated successfully, but these errors were encountered: