Description of problem:
Seems that the version of Openssl on RHEl 6 and RHEL 7 :OpenSSL 1.0.1e-fips 11 Feb 2013 and do not provide secp256k1.
1. Proposed title of this feature request
>>>Enable curve secp256k1 in OpenSSL
2. Who is the customer behind the request?
Account: name and acct # 1319153 Etes GmbH
TAM customer: no
SRM customer: no
3. What is the nature and description of the request?
>>curve secp256k1 in OpenSSL is enabled for Fedora and likely needs to be included in RHEL
4. Why does the customer need this? (List the business requirements here)
>>>There is not yet a specific business requirement, however they think that having the same cryptography options like in Fedora avoids a lack of them at a later time. The intention is to query this early with lower priority in order to hopefully have this feature at a later time when it is needed.
5. How would the customer like to achieve this? (List the functional requirements here)
>>>enable the curve in the OpenSSL
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
>>>No specific timeline. RHEL 7, RHEL 6
9. Is the sales team involved in this request and do they have any additional input?
10. List any affected packages or components.
11. Would the customer be able to assist in testing this functionality if implemented?
Version-Release number of selected component (if applicable):OpenSSL 1.0.1e
Steps to Reproduce:
1.Run the following command to check for the list of available ciphers:
[bkundal@bkundal ~]$ openssl ecparam -list_curves
secp384r1 : NIST/SECG curve over a 384 bit prime field
prime256v1: X9.62/SECG curve over a 256 bit prime field
This does not list the secp256k1
curve secp256k1 in OpenSSL is enabled for Fedora
*** Bug 1324263 has been marked as a duplicate of this bug. ***
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.