RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1080128 - Backport automatic selection of curves for ECDHE
Summary: Backport automatic selection of curves for ECDHE
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openssl
Version: 7.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: Alicja Kario
URL:
Whiteboard:
Depends On: 1080127
Blocks: 1080125 1153579
TreeView+ depends on / blocked
 
Reported: 2014-03-24 17:56 UTC by Alicja Kario
Modified: 2016-07-12 16:03 UTC (History)
3 users (show)

Fixed In Version: openssl-1.0.1e-37.el7
Doc Type: Enhancement
Doc Text:
Feature: Allow the TLS server to automatically select the ECC curve from among the curves supported by the TLS client. Reason: In the previous OpenSSL package the curve that TLS server supports could be chosen only by the server implementation and could not be automatically selected from a set which was too restrictive and clients which do not support that pre-selected curve could not use ECDH cipher suites. Result: The server can now automatically choose a curve from the list of curves supported by the client. However this needs to be appropriately enabled by API call in the concrete TLS server implementation.
Clone Of:
Environment:
Last Closed: 2015-03-05 11:03:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1352941 0 unspecified CLOSED Backport automatic selection of curves for ECDHE in DTLS 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2015:0478 0 normal SHIPPED_LIVE openssl bug fix and enhancement update 2015-03-05 15:44:08 UTC

Internal Links: 1352941

Description Alicja Kario 2014-03-24 17:56:51 UTC 
Description of problem:
According to RFC 4492 (page 10, section 4; http://tools.ietf.org/html/rfc4492#page-10), the server MUST select a curve supported by the client. Current API does allow only hardcoding the selected curve on context initialisation.

Version-Release number of selected component (if applicable):
openssl-1.0.1e-33.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Setup server that supports all NIST curves, provide nistp256 curve as preferred for ECDHE negotiation
2. Connect to server using client that supports only nistp384 curve

Actual results:
Connection is aborted

Expected results:
Connection is successful

Additional info:
Bug 1080127 will need to be resolved for automatic verification.
Comment 12 Jiri Herrmann 2014-12-12 15:32:22 UTC 
If this Feature should be included in the 7.1 Release Notes, could you please change the Doc Type from Enhancement to "Release Note"?

Note that the Release Notes are intended to list the most prominent and customer-relevant new features rather than every single enhancement.

Cheers,
Jirka
Comment 13 Tomas Mraz 2015-01-02 10:13:00 UTC 
No release note needed.
Comment 15 errata-xmlrpc 2015-03-05 11:03:00 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://rhn.redhat.com/errata/RHBA-2015-0478.html
Note You need to log in before you can comment on or make changes to this bug.