import/path: issue title

[dosgo]

Go version

go version go1.22.7 windows/amd64

Output of go env in your module/workspace:

set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\DosGo\AppData\Local\go-build
set GOENV=C:\Users\DosGo\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\DosGo\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\DosGo\go
set GOPRIVATE=
set GOPROXY=direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLCHAIN=auto
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.22.7
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=D:\go\src\adbtest\go.mod
set GOWORK=
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=C:\Users\DosGo\AppData\Local\Temp\go-build2525950035=/tmp/go-build -gno-record-gcc-switches

What did you do?

The following code keeps returning remote error: tls: certificate required, but it works fine with GetClientCertificate. Golang's own tls server does not need to set GetClientCertificate and works fine.

func main() {
	conn, err := net.Dial("tcp", "192.168.78.34:33285")
	certificates, err := tls.LoadX509KeyPair("cerm.pem", "test.key")
	if err != nil {
		fmt.Printf("certificates error err:%+v\r\n", err)
		return
	}
	tlsConfig := tls.Config{
		MinVersion: tls.VersionTLS13,
		MaxVersion: tls.VersionTLS13,
		Certificates: []tls.Certificate{
			certificates,
		},
		InsecureSkipVerify: true,
	}
	tlsconn := tls.Client(conn, &tlsConfig)
	message_raw := make([]byte, 1024)
	_, err = io.ReadFull(tlsconn, message_raw)
}

What did you see happen?

err:remote error: tls: certificate required

What did you expect to see?

The tls.config Certificates parameter works fine, not sure if the problem is with the server or the tls client.

[gabyhelp]

Related Issues and Documentation

• affected/package: TLS #60719 (closed)
• crypto/tls: RequireAndVerifyClientCert is not working as intended. #63122 (closed)
• crypto/tls: RequireAndVerifyClientCert is not working as intended. #63120 (closed)
• crypto/tls: client did not fail when lack of a certificate and server requires one #59012 (closed)
• crypto/tls: Dial to server with invalid client certificates succeeds and allows writes on tip, but not in 1.12 #32202 (closed)
• crypto/tls: client certificate not sent #23924 (closed)
• net/http/httptest: Server does not check GetCertificate #63812
• crypto/tls: Dial to TLS endpoint requiring ClientAuth does not error #33368 (closed)
• crypto/tls: RSA key missing NULL parameters help #30205 (closed)
• net/http: Client cert auth with TLSClientConfig Certificates is not working while using GetCertificates works #34258 (closed)

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[seankhliao]

sounds like a problem with your server.

[dosgo]

Mainly, both rust and java can be connected