Bug 1374740 - libcurl does not accept use of ciphers *-SHA384
Summary: libcurl does not accept use of ciphers *-SHA384
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: curl
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Kamil Dudka
QA Contact: Karel Srot
URL:
Whiteboard:
Depends On:
Blocks: 1380361
TreeView+ depends on / blocked
 
Reported: 2016-09-09 13:52 UTC by Martin Poole
Modified: 2017-08-01 17:02 UTC (History)
4 users (show)

Fixed In Version: curl-7.29.0-39.el7
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-08-01 17:02:31 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2016 0 normal SHIPPED_LIVE Moderate: curl security, bug fix, and enhancement update 2017-08-01 18:02:02 UTC

Description Martin Poole 2016-09-09 13:52:36 UTC 
Description of problem:

the nss.c of libcurl does not accept the following NSS supported ciphers

#define TLS_RSA_WITH_AES_256_GCM_SHA384         0x009D
#define TLS_DHE_RSA_WITH_AES_256_GCM_SHA384     0x009F
#define TLS_DHE_DSS_WITH_AES_256_GCM_SHA384     0x00A3
#define TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 0xC024
#define TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384   0xC028
#define TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 0xC02C
#define TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   0xC030


Version-Release number of selected component (if applicable):

curl-7.29.0-35.el7
Comment 2 Kamil Dudka 2016-09-09 14:09:52 UTC 
Confirmed.  There is more cipher-suites missing in the list...
Comment 3 Kamil Dudka 2016-09-22 08:53:39 UTC 
upstream commits:
https://github.com/curl/curl/commit/75912202
https://github.com/curl/curl/commit/049aa925
https://github.com/curl/curl/commit/d1f1c857
Comment 13 errata-xmlrpc 2017-08-01 17:02:31 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2016
Note You need to log in before you can comment on or make changes to this bug.