Bug 436781

Summary:	curl does not use strongest ciphers by default
Product:	[Fedora] Fedora	Reporter:	Till Maas <opensource>
Component:	curl	Assignee:	Kamil Dudka <kdudka>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	10	CC:	jnovy, kdudka, opensource
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	curl-7.19.4-5.fc11	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-03-18 17:15:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Till Maas 2008-03-10 14:05:33 UTC

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

Comment 1 Bug Zapper 2008-11-26 10:06:39 UTC

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

Comment 2 Till Maas 2008-12-08 07:22:27 UTC

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.

Comment 3 Kamil Dudka 2009-03-17 12:57:01 UTC

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.

Comment 4 Kamil Dudka 2009-03-18 17:15:38 UTC

built as curl-7.19.4-5.fc11