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
https://play.golang.org/p/YJUDxQHX8t1
No output.
2018/11/26 11:44:22 remote error: tls: internal error 2018/11/26 11:44:22 tls: unsupported certificate key (*ecdsa.PrivateKey) exit status 1
No.
go version devel +9fe9853ae5 Mon Nov 26 14:13:53 2018 +0000 darwin/amd64 GOARCH="amd64" GOBIN="" GOCACHE="/Users/benburkert/Library/Caches/go-build" GOEXE="" GOFLAGS="" GOHOSTARCH="amd64" GOHOSTOS="darwin" GOOS="darwin" GOPATH="/Users/benburkert" GOPROXY="" GORACE="" GOROOT="/Users/benburkert/src/github.com/golang/go" GOTMPDIR="" GOTOOLDIR="/Users/benburkert/src/github.com/golang/go/pkg/tool/darwin_amd64" GCCGO="gccgo" CC="clang" CXX="clang++" CGO_ENABLED="1" GOMOD="" GOROOT/bin/go version: go version devel +9fe9853ae5 Mon Nov 26 14:13:53 2018 +0000 darwin/amd64 GOROOT/bin/go tool compile -V: compile version devel +9fe9853ae5 Mon Nov 26 14:13:53 2018 +0000 uname -v: Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64 ProductName: Mac OS X ProductVersion: 10.13.6 BuildVersion: 17G65 lldb --version: lldb-1000.11.37.1 Swift-4.2
The text was updated successfully, but these errors were encountered:
This error pops up because tip defaults to TLS1.3, and throwing an error is the right thing to do, but the message is confusing because *ecdsa.PrivateKey is supported, but not with the chosen curve.
*ecdsa.PrivateKey
Sorry, something went wrong.
/cc @FiloSottile
I’ll improve the error message.
Change https://golang.org/cl/151661 mentions this issue: crypto/tls: improve error message for unsupported certificates in TLS 1.3
crypto/tls: improve error message for unsupported certificates in TLS 1.3
950100a
No branches or pull requests
What did you do?
https://play.golang.org/p/YJUDxQHX8t1
What did you expect to see?
No output.
What did you see instead?
Does this issue reproduce with the latest release (go1.11.2)?
No.
System details
The text was updated successfully, but these errors were encountered: