Last active
December 30, 2015 06:29
-
-
Save jcsalterego/7789998 to your computer and use it in GitHub Desktop.
sslv2 alert handshake failure
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
$ lsb_release -a | |
No LSB modules are available. | |
Distributor ID: Ubuntu | |
Description: Ubuntu 12.04 LTS | |
Release: 12.04 | |
Codename: precise | |
$ curl --version | |
curl 7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3 | |
Protocols: dict file ftp ftps gopher http https imap imaps ldap pop3 pop3s rtmp rtsp smtp smtps telnet tftp | |
Features: GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP | |
$ curl --verbose https://sitestream.twitter.com/ | |
* About to connect() to sitestream.twitter.com port 443 (#0) | |
* Trying 199.59.148.137... connected | |
* successfully set certificate verify locations: | |
* CAfile: none | |
CApath: /etc/ssl/certs | |
* SSLv3, TLS handshake, Client hello (1): | |
* SSLv3, TLS alert, Server hello (2): | |
* error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure | |
* Closing connection #0 | |
curl: (35) error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure | |
$ openssl s_client -connect sitestream.twitter.com:443 | |
CONNECTED(00000003) | |
139698172339872:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:724: | |
--- | |
no peer certificate available | |
--- | |
No client certificate CA names sent | |
--- | |
SSL handshake has read 7 bytes and written 174 bytes | |
--- | |
New, (NONE), Cipher is (NONE) | |
Secure Renegotiation IS NOT supported | |
Compression: NONE | |
Expansion: NONE | |
--- |
lfcipriani
commented
Dec 4, 2013
This was a curl bug. Please upgrade your curl
.
See: How to fix curl sslv3 alert handshake failure?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment