Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1516518

Summary: Update downstream patch nss-3.16-token-init-race.patch for NSS 3.34+
Product: Red Hat Enterprise Linux 6 Reporter: Kai Engert (:kaie) (inactive account) <kengert>
Component: nssAssignee: Bob Relyea <rrelyea>
Status: CLOSED ERRATA QA Contact: Stefan Dordevic <sdordevi>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.10CC: dueno, hkario, jkurik, mthacker, rrelyea, sdordevi, szidek
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: nss-3.34.0-3.el6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-19 05:10:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1485481    

Description Kai Engert (:kaie) (inactive account) 2017-11-22 19:45:31 UTC
We have a downstream patch that is no longer compatible with NSS 3.34+

The original issue hasn't been fixed upstream yet, the downstream fix is still required.

We must develop an updated downstream patch.

This blocks the rebase of NSS for Firefox 58, bug 1485481.

Original upstream bug related to the old patch:

Recent upstream bug that caused the old patch to become incompatible:

Comment 2 Bob Relyea 2017-12-05 01:35:55 UTC
I've attached an untested patch to upstream bug: which implements my suggestion in comment

Comment 14 errata-xmlrpc 2018-06-19 05:10:10 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.