Re: [go-nuts] Client certificate in request missing

2018-02-19 Thread Miha Zoubek
Hello i tried this certificates also with Nodejs and there it is working on first try, so certificates should be ok. Only difference is that i did not

Re: [go-nuts] Client certificate in request missing

2018-02-19 Thread Miha Zoubek
Here is screen shot. I tried the same certificates with NodeJs and there is working on first shot, but really do not want to use NodeJs for this :) I Dne

Re: [go-nuts] Client certificate in request missing

2018-02-19 Thread Maciej Gałkowski
Ah, just had a closer look at the screenshot. It seems that the server sends Certificate Request message. The Certificate Request contains a list of all CA RDNs that are accepted by the server, (which can be an empty list, in which case cert signed by CA should be accepted). It would be

Re: [go-nuts] Client certificate in request missing

2018-02-19 Thread Maciej Gałkowski
Hi, This might be a red herring, but are you sure that your server requires a client cert? As far as I can understand the RFC https://tools.ietf.org/html/rfc5246#section-7.4.4, it is the server that sends a certificate request to the client so it can authenticate. W dniu poniedziałek, 19

Re: [go-nuts] Client certificate in request missing

2018-02-19 Thread Miha Zoubek
Hello tnx for help. I tried like: tlsConfig := { Certificates: []tls.Certificate{cert}, RootCAs: caCertPool, InsecureSkipVerify: false, } //tlsConfig.BuildNameToCertificate() transport := {TLSClientConfig: tlsConfig} client := {Transport: transport}

Re: [go-nuts] Client certificate in request missing

2018-02-19 Thread Jakob Borg
Try without using Config.BuildNameToCertificate. That’s a server side thing and I doubt it does what you want on the client side. //jb On 16 Feb 2018, at 14:41, mzou...@gmail.com wrote: Hello this is my code: https://play.golang.org/p/yxhYXEVMPjB I got certificate