Re: [twsocket] Should I be concerned about https://cert-test.sandbox.google.com?

2015-11-03 Thread Albert Wiersch
> > Again the HTTPS sample works fine, make sure you have set SslECDHMethod to > sslECDHAuto. Yep. That was it! Thanks again. One more question... I can leave it always set to auto, right? This should make the component connect successfully to more servers rather than less, correct? Thanks,

[twsocket] Should I be concerned about https://cert-test.sandbox.google.com?

2015-11-03 Thread Albert Wiersch
Angus, Here's another issue... I can't open this URL either (with v8.18): https://cert-test.sandbox.google.com I get: SslHandshakeErrCode> 1049 (0 if no error) SslHandshakeRespMsg> error:14077419:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert access denied Should I be concerned? More info:

Re: [twsocket] Should I be concerned about https://cert-test.sandbox.google.com?

2015-11-03 Thread Angus Robertson - Magenta Systems Ltd
> I can leave it always set to auto, right Yes, Auto is fine for clients, EC is only used if the server cipher suite requests it and is otherwise ignored. Auto only actually works with OpenSSL 1.0.2 and later, otherwise falls back to sslECDH_P256, but the rule now seems to be use the

Re: [twsocket] Should I be concerned about https://cert-test.sandbox.google.com?

2015-11-03 Thread Angus Robertson - Magenta Systems Ltd
> Here's another issue... I can't open this URL either (with v8.18): > https://cert-test.sandbox.google.com Again the HTTPS sample works fine, make sure you have set SslECDHMethod to sslECDHAuto. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto