Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1374740 - libcurl does not accept use of ciphers *-SHA384
libcurl does not accept use of ciphers *-SHA384
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: curl (Show other bugs)
7.3
Unspecified Unspecified
unspecified Severity medium
: rc
: ---
Assigned To: Kamil Dudka
Karel Srot
: Patch
Depends On:
Blocks: 1380361
  Show dependency treegraph
 
Reported: 2016-09-09 09:52 EDT by Martin Poole
Modified: 2017-08-01 13:02 EDT (History)
4 users (show)

See Also:
Fixed In Version: curl-7.29.0-39.el7
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-01 13:02:31 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2016 normal SHIPPED_LIVE Moderate: curl security, bug fix, and enhancement update 2017-08-01 14:02:02 EDT

  None (edit)
Description Martin Poole 2016-09-09 09:52:36 EDT
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 10:09:52 EDT
Confirmed.  There is more cipher-suites missing in the list...
Comment 13 errata-xmlrpc 2017-08-01 13:02:31 EDT
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.