Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionElio Maldonado Batiz
2013-08-28 23:17:13 UTC
Description of problem: The version of nss-softoken that nss must require is the last one that received FIPS 140 validation or in some cases the one being prepared for submission for validation.
Bug 962465 reported the case where nss was built against and incorrect version of nss-softoken and the ensuing problems.
Version-Release number of selected component (if applicable):
How reproducible: Once
Steps to Reproduce: From Bug 962465
1. rebuild nss against new nss-softokn
2. install the packages on a system with old nss-softokn
3. curl -svo/dev/null https://google.com
Actual results:
curl does not work
Expected results:
curl should work.
Additional info:
Either updating nss-softokn or rebuilding nss against the old one fixes the problem. By the old is meant nss-softoken-3.12.9 which was the last version to be FIPS validated. By the new one I assume is the one being worked on for the sumbmition but I am not sure.
The investigation as to the causes should be completed and the the necessary modification to the nss.spec made to ensure we build with the correct version of nss-softoken. If the incorrect version is the one tagged into the buildroot override the brew should fail.
Comment 2Elio Maldonado Batiz
2013-08-28 23:40:54 UTC
From Bob Relyea's email where he requsted I enter this bug:
>BTW Elio, see comment 16 in the bug. It suggests you open a bug to
>investigate why there was a problem with the mismatched softokens. That
>bug should not be targetted for RHEL-6.5.
^^^
>Then tell QE that they can verify this bug by inspection of the nss.spec file.
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.
http://rhn.redhat.com/errata/RHBA-2014-1378.html