> Did you try the sample application? I took a quick look at the code to figure out SslHandshakeRespMsg.
> It shows how to restrict which SSL/TLS versions are used, and how errors > are > reported. There were a lot of SSL changes over the last six months to > support the > latest protocols. When I connect to my own server, it works with this: SSL Connected OK with TLSv1.2, cipher DHE-RSA-AES256-GCM-SHA384, key exchange DH, encryption AESGCM(256), message authentication AEAD So I would assume it's using TLSv1.2, so why won't it connect with that for https://developer.mozilla.org/en-US/docs/Web/HTML/Element/address? Perhaps I need to disable SSLv3 for that site? I am not "SSL" expert but I wonder why it can't connect using TLSv1.2 even if SSLv3 is also enabled. I'm curious... perhaps I should now disable SSLv3 by default? I'll have a look at the sample app and hope it will answer some of my questions. Just found this: http://www.theregister.co.uk/2015/06/26/that_shot_you_heard_sslv3_is_now_dead/ It says: "Pragmatically, clients MUST NOT send a ClientHello with ClientHello.client_version set to {03,00}. Similarly, servers MUST NOT send a ServerHello with ServerHello.server_version set to {03,00}. Any party receiving a Hello message with the protocol version set to {03,00} MUST respond with a "protocol_version" alert message and close the connection." So maybe that server is set to dump/close my request. Thanks! Albert -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
