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 1404815 - SEC_ERROR_NO_TOKEN error when using SSL and multiple threads
Summary: SEC_ERROR_NO_TOKEN error when using SSL and multiple threads
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: curl
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Kamil Dudka
QA Contact: Karel Srot
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-14 17:44 UTC by Jan Dobes
Modified: 2017-08-01 17:02 UTC (History)
3 users (show)

Fixed In Version: curl-7.29.0-39.el7
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
: 1413619 (view as bug list)
Environment:
Last Closed: 2017-08-01 17:02:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1413619 0 unspecified CLOSED SEC_ERROR_NO_TOKEN error when using SSL and multiple threads 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHSA-2017:2016 0 normal SHIPPED_LIVE Moderate: curl security, bug fix, and enhancement update 2017-08-01 18:02:02 UTC

Internal Links: 1413619

Description Jan Dobes 2016-12-14 17:44:58 UTC 
Description of problem:
When I'm using pycurl + threading modules with SSL in python, execution will crash with SEC_ERROR_NO_TOKEN error coming from libcurl.

Version-Release number of selected component (if applicable):
python-pycurl-7.19.0-19.el7.x86_64
libcurl-7.29.0-35.el7.x86_64
nss-3.21.3-2.el7_3.x86_64

How reproducible:
almost always

Steps to Reproduce:
1. Try to download multiple files in multiple threads from server requiring SSL client certificates

Actual results:
pycurl perform() calls will crash

Expected results:
works without problems

Additional info:
https://bugzilla.mozilla.org/show_bug.cgi?id=1297397
https://github.com/curl/curl/commit/3a5d5de9ef52ebe8ca2bda2165edc1b34c242e54
Comment 1 Kamil Dudka 2016-12-14 21:34:28 UTC 
(In reply to Jan Dobes from comment #0)
> Description of problem:
> When I'm using pycurl + threading modules with SSL in python, execution will
> crash with SEC_ERROR_NO_TOKEN error coming from libcurl.

Yes, this is a known bug of NSS as you have already figured out.

> How reproducible:
> almost always

It was not that easy to reproduce in my environment when I tried it recently.

> Actual results:
> pycurl perform() calls will crash

If it returns SEC_ERROR_NO_TOKEN, it is not really a crash, just a spurious failure.  A python script may crash if the exception is not handled, but that is another story.

> Additional info:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1297397

We should probably create a RHEL-7 bug for this to force NSS maintainers sponsored by Red Hat to at least have a look.  It is a bug of NSS after all.  If you have a business justification, it would also help.

> https://github.com/curl/curl/commit/3a5d5de9ef52ebe8ca2bda2165edc1b34c242e54

I am fine with including the above patch in a RHEL-7 update.  It will fix only libcurl-based applications though.
Comment 3 Kamil Dudka 2017-01-16 12:26:43 UTC 
follow-up commit upstream:

https://github.com/curl/curl/commit/25ed9ea5
Comment 4 Kai Engert (:kaie) (inactive account) 2017-01-16 14:28:42 UTC 
Kamil, is this issue limited to RHEL 7, not RHEL 6 ?
Comment 5 Kamil Dudka 2017-01-16 14:57:16 UTC 
(In reply to Kai Engert (:kaie) from comment #4)
> Kamil, is this issue limited to RHEL 7, not RHEL 6 ?

The bug in NSS source code must be in both of them but I was debugging it on RHEL-7 only.
Comment 6 Kamil Dudka 2017-01-24 12:35:51 UTC 
This bug neither blocks, nor depends on bug #1413619.  In other words, each of them can fixed without fixing the other bug first.  I am weakening the relation to See Also.
Comment 16 errata-xmlrpc 2017-08-01 17:02:31 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/RHSA-2017:2016
Note You need to log in before you can comment on or make changes to this bug.