Re: [go-nuts] Handshake failed when using builtin TLS package: no cipher suite supported by both client and server

For history: we've made it work with Let's Encrypt issued certificates too: adding *ForceRSA: true* to autocert.Manager did the trick. четверг, 9 февраля 2017 г., 10:48:08 UTC+3 пользователь Alexandr Emelin написал: > > Just tried trial certificate from Comodo - it works! So the p

Re: [go-nuts] Handshake failed when using builtin TLS package: no cipher suite supported by both client and server

09:44 AM, Alexandr Emelin wrote: > > Chrome 49 on Windows XP SP3 > > Are you using a cert from let's encrypt? There have been issues in the > past (although LE officially lists Windows XP with SP3 as supported), > check these links out: > > > https://github.com/certbot

[go-nuts] Re: Handshake failed when using builtin TLS package: no cipher suite supported by both client and server

kuapp.com#3605008a4b977a443f4f14e3c072d362c55475e7797b46554cc3088f8cbfa11b> TLS 1.2 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 ECDH secp256r1 FS вторник, 7 февраля 2017 г., 14:59:42 UTC+3 пользователь Alexandr Emelin написал: > > James, thanks for response. I am using go1.7.5 linux/amd64 > > I have no t

[go-nuts] Re: Handshake failed when using builtin TLS package: no cipher suite supported by both client and server

default tls.Config? > > I don't have that client directly available to test with, but does your > particular client show the expected information when you visit > https://www.ssllabs.com/ssltest/viewMyClient.html? > > > On Sunday, February 5, 2017 at 3:44:47 AM UTC-5, Alexandr Emel

[go-nuts] Handshake failed when using builtin TLS package: no cipher suite supported by both client and server

When using builtin TLS for http/websocket server I noticed that handshakes from some old browser clients fail. The reason why I find this strange is that other TLS implementations work with those connections without any problems. I used ssllabs.com/ssltest/ to