On Saturday, August 22, 2015 2:18 PM, Daniel Stenberg <daniel_at_haxx.se> wrote:
   

 On Sat, 22 Aug 2015, Lenny Markus via curl-users wrote:

> Thanks.  How could I force curl to use a specify cipher in this case?

--ciphers, see http://curl.haxx.se/docs/manpage.html#--ciphers

> (I thought curl relied on the underlying openSSL library to establish the
> crypto/ssl handshake)

It does (assuming your curl was built with openSSL).

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html
Etiquette:  http://curl.haxx.se/mail/etiquette.html
This still baffles me.I forced curl to use the exact same settings that work with openssl s_client, and I get the same result
$ curl -vv --tlsv1.2 --cipher ECDHE-RSA-AES256-SHA384 https://ms136.slack-msgs.com
* Rebuilt URL to: https://ms136.slack-msgs.com/
*   Trying 54.175.159.82...
* Connected to ms136.slack-msgs.com (54.175.159.82) port 443 (#0)
* ALPN, offering http/1.1
* Cipher selection: ECDHE-RSA-AES256-SHA384
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: none
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* Unknown SSL protocol error in connection to ms136.slack-msgs.com:443 
* Closing connection 0
curl: (35) Unknown SSL protocol error in connection to ms136.slack-msgs.com:443
I've built this from scratch, linking to the latest openSSL.Any ideas what else I could check or try?
  

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ: http://curl.haxx.se/docs/faq.html
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2015-08-23