Red Hat Bugzilla – Bug 436781
curl does not use strongest ciphers by default
Last modified: 2009-03-18 13:15:38 EDT
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce 1.setup a webserver that supports only ssl ciphers "DHE-RSA-AES256-SHA:AES256-SHA" (OpenSSL definitions) at example.com 2.curl https://example.com" 3.curl --ciphers "rsa_aes_256_sha" "https://example.com Actual results: The second step shows the following error: curl: (35) SSL connect error But the third one works. Expected results: Curl should also connect in the second step, because the ciphers that are provided by the server are secure. By default, curl uses SSL_RSA_WITH_RC4_128_MD5 to connect to bugzilla.redhat.com instead of e.g. a AES 256 cipher, that are also supported by bugzilla.redhat.com
This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Still an issue with F10, curl-7.18.2-7.fc10: $ curl --silent --trace-ascii - -I https://bugzilla.redhat.com | grep SSL == Info: SSL connection using SSL_RSA_WITH_RC4_128_MD5 $ curl --silent --trace-ascii - --ciphers "rsa_aes_256_sha" -I https://bugzilla.redhat.com | grep SSL == Info: SSL connection using TLS_RSA_WITH_AES_256_CBC_SHA I assume that F9 is then affected, too.
http://www.mozilla.org/projects/security/pki/nss/nss-3.4/nss-3.4-release-notes.html Following ciphers are new in NSS 3.4 and not enabled by default: TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA I am going to write a patch to enable them within curl library.
built as curl-7.19.4-5.fc11