No, it doesn't. It is you who ask for a legacy protocol. Why do you insist on SSLv3 to begin with? The rest of the world tries to move away from it and that server speaks TLS1.2 just fine!

---
** [bugs:#1447] Cannot communicate securely with peer: no common encryption algorithm(s)**
**Status:** pending-invalid
**Created:** Fri Nov 07, 2014 11:17 AM UTC by Vladimir
**Last Updated:** Sun Nov 09, 2014 06:17 PM UTC
**Owner:** Daniel Stenberg
curl 7.29.0 (x86_64-redhat-linux-gnu) libcurl/7.29.0 NSS/3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2 (CentOS 6.5)
$ curl -v -S -k -3 https://www.laguidatv.it
* About to connect() to www.laguidatv.it port 443 (#0)
*   Trying 5.9.120.232...
* Connected to www.laguidatv.it (5.9.120.232) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* NSS error -12286 (SSL_ERROR_NO_CYPHER_OVERLAP)
* Cannot communicate securely with peer: no common encryption algorithm(s).
* Closing connection 0
curl: (35) Cannot communicate securely with peer: no common encryption algorithm(s)
---
Sent from sourceforge.net because curl-tracker@cool.haxx.se is subscribed to https://sourceforge.net/p/curl/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/curl/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.