Revolving around the core of technology
Two days ago I updated syncrify. Now clients cannot connect, but server is running and I can connect with telnet, so it's not a network problem. Please help.
339 [main] ERROR com.synametrics.syncrify.client.cX - Unable to connect to the server. Received fatal alert: handshake_failure
javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.Alerts.getSSLException(Alerts.java:154)
at sun.security.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1763)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1006)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1190)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1217)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1201)
at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:423)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:979)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:250)
at com.synametrics.syncrify.client.cX.a(Unknown Source)
at com.synametrics.syncrify.client.cX.a(Unknown Source)
at com.synametrics.syncrify.client.L.a(Unknown Source)
at com.synametrics.syncrify.client.SyncrifyClient.main(Unknown Source)
Unable to connect to the server.
Thanks...
Marco,
Please upgrade to build 834, which takes care of this problem.
On October 22, 2014 we released build 833 that disabled SSLv3 protocol in Syncrify. This was done as a result of newly discovered POODLE problem. Although this change worked with most clients, some clients running on older operation systems (Windows XP and older LInux) failed to communicate with the server with the following error:
fatal alert: handshake_failure
Build 834 adds support for SSLv2Hello protocol, which allows these older clients to connect. SSLv3 is still disabled and therefore, POODLE attack is not possible.
Regards,
Imran