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 1854369 - curl cannot use the openssl engine like pkcs11
Summary: curl cannot use the openssl engine like pkcs11
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: curl
Version: 8.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: 8.0
Assignee: Kamil Dudka
QA Contact: Daniel Rusek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-07 10:06 UTC by Masahiro Matsuya
Modified: 2020-11-04 02:16 UTC (History)
1 user (show)

Fixed In Version: curl-7.61.1-13.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 02:16:24 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4599 0 None None None 2020-11-04 02:16:35 UTC

Description Masahiro Matsuya 2020-07-07 10:06:35 UTC 
Description of problem:

curl cannot use the openssl engine.
Please include this upstream patch:
   https://github.com/curl/curl/commit/e2dd435d473cdc97785df95d032276fafb4b7746

HAVE_ENGINE_LOAD_BUILTIN_ENGINES macro isn't used any more, since it's replaced by USE_OPENSSL_ENGINE.
Just one macro is remaining and it caused a problem to load the openssl engines.


Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 8

How reproducible:
Always

Steps to Reproduce:

1. Setup openssl engines by changing /etc/pki/tls/openssl.cnf


@@ -29,6 +29,7 @@ openssl_conf = default_modules
 [ default_modules ]
 
 ssl_conf = ssl_module
+engines = engine_section
 
 [ ssl_module ]
 
@@ -366,3 +367,12 @@ ess_cert_id_chain	= no	# Must the ESS ce
 				# (optional, default: no)
 ess_cert_id_alg		= sha1	# algorithm to compute certificate
 				# identifier (optional, default: sha1)
+
+
+[engine_section]
+pkcs11 = pkcs11_section
+
+[pkcs11_section]
+engine_id = pkcs11
+dynamic_path = /usr/lib64/engines-1.1/libpkcs11.so
+init = 0


2. run openssl command to confirm if the engine is configured.

# openssl engine -t
(rdrand) Intel RDRAND engine
     [ available ]
(dynamic) Dynamic engine loading support
     [ unavailable ]
(pkcs11) pkcs11 engine
     [ available ]

 
3. run curl commands

# curl --engine list
Build-time engines:
  <none>

# curl --engine pkcs11 https://bugzilla.redhat.com
curl: (53) SSL Engine 'pkcs11' not found



Actual results:
curl cannot use the openssl engines.


Expected results:
curl can use the openssl engines.
Comment 8 errata-xmlrpc 2020-11-04 02:16:24 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 (Moderate: curl security and bug fix update), 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-2020:4599
Note You need to log in before you can comment on or make changes to this bug.