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 1444860 - PKCS #11 slot leakage hampers unload of nss-pem
Summary: PKCS #11 slot leakage hampers unload of nss-pem
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: curl
Version: 7.4
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Kamil Dudka
QA Contact: Stefan Dordevic
URL:
Whiteboard:
Depends On:
Blocks: 1465901
TreeView+ depends on / blocked
 
Reported: 2017-04-24 12:46 UTC by Kamil Dudka
Modified: 2018-04-10 11:46 UTC (History)
2 users (show)

Fixed In Version: curl-7.29.0-43.el7
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
: 1445392 (view as bug list)
Environment:
Last Closed: 2018-04-10 11:45:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
[WIP] test-case patch (2.65 KB, patch)
2018-02-09 11:43 UTC, Kamil Dudka
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0732 0 None None None 2018-04-10 11:46:17 UTC

Description Kamil Dudka 2017-04-24 12:46:54 UTC
Description of problem:
The PKCS #11 slot object returned by SECMOD_WaitForAnyTokenEvent() is leaked, which later prevents nss-pem from being unloaded.


Version-Release number of selected component (if applicable):
curl-7.29.0-42.el7


Steps to Reproduce:
1. install nss-pem-1.0.3-2.el7
2. load a private key from file using libcurl


Actual results:
nss-pem fails to unload


Expected results:
nss-pem unloads properly


Additional info:
This bug was revealed by the following nss-pem commit:
https://github.com/kdudka/nss-pem/commit/eefef228

Unfortunately, reverting the commit would reintroduce the one second sleep after loading a private key, which is something we do not want to do?

Comment 2 Kamil Dudka 2017-04-25 12:17:12 UTC
upstream commit:

https://github.com/curl/curl/commit/curl-7_54_0-24-gc8ea86f

Comment 3 Kamil Dudka 2017-04-25 14:48:07 UTC
Removing the Regression keyword.  The bug is triggered by a change in nss-pem, so the change will be reverted.

Comment 8 Kamil Dudka 2017-09-13 08:12:53 UTC
This can be tested by the test for bug #1445384 with patched nss-pem (after reverting the revert).

Comment 14 Kamil Dudka 2018-02-09 11:43:15 UTC
Created attachment 1393709 [details]
[WIP] test-case patch

Please clone /CoreOS/curl/Regression/bz694294-curl-AND-nss-need-to-be-able-to-use-pem-files and apply the attached patch on top if it.

It fails with:
libcurl-7.29.0-42.el7
nss-pem-1.0.3-2.el7

... but passes with:
libcurl-7.29.0-46
nss-pem-1.0.3-2.el7

Comment 18 errata-xmlrpc 2018-04-10 11:45:43 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/RHBA-2018:0732


Note You need to log in before you can comment on or make changes to this bug.