SSL23_GET_SERVER_HELLO: crash when sslv3 message fails

I just installed a new version of gitlab, after a fresh install of ssl doesn't work ... it gives SSL23_GET_SERVER_HELLO: sslv3 message. ssh works fine. the only difference I see is that the old browser says it uses TLS 1.0 and the newer version says it uses 1.2. Since this is not gitlab related, I am posting the issue on stackoverflow ...

$ git clone https://gitlabserver/group/project.git
Cloning into 'project'...
* Couldn't find host gitlabserver in the _netrc file; using defaults
* Adding handle: conn: 0x282d6f8
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x282d6f8) send_pipe: 1, recv_pipe: 0
* About to connect() to gitlabserver port 443 (#0)
*   Trying gitlabserver...
* Connected to gitlabserver port 443 (#0)
* successfully set certificate verify locations:
*   CAfile: c:/Users/lanid/curl-ca-bundle.crt
  CApath: none
* error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure

* Closing connection 0
fatal: unable to access 'https://gitlabserver/group/project.git/': error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure

      

Here is the OpenSSL result s_client

when tested with TLS 1.0 and SNI:

openssl s_client -connect <hostname>:<port> -tls1 -servername <hostname>

Loading 'screen' into random state - done
CONNECTED(00000208)
8008:error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure:.\ssl\s3_pkt.c:1126:SSL alert number 40
8008:error:1409E0E5:SSL routines:SSL3_WRITE_BYTES:ssl handshake failure:.\ssl\s3_pkt.c:547:

      

Same command for another server with the same setup, but the old version file works ...

+5


source to share


4 answers


Updating openssl resolved this issue ...



+3


source


If you are facing this issue on Git Client.

Then install the latest version of Git Bash.



I faced the same problem and decided to install a new Git Client.

+3


source


Updating OpenSSL should fix your problems.

OpenSSL has had some serious vulnerabilities discovered recently. In addition, many web servers on the Internet have tightened security to block these vulnerable protocols and ciphers.

+2


source


Everyone using GitGUI solved the problem ...

0


source







All Articles