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.
Description of problem:
The lab has identified a potential issue in the DRBG, where NIST has been more strict in the past. We may need to create a patch to fix this DRBG deficiency.
This bug is a place holder until more specifics are known.
Testing:
This patch is FIPS related. It requires running a set of builtin tests at POST time and when we reseed. I don't believe there is a way to inject a failure of these tests from outside, so they can only be 'tested' by inspection.
There are elements of the tests that can be detected using the FIPS test tool (used for algorithm testing). I'll supply some instructions on how to do that.
The only other testing is regression testing. Any FIPS smoke tests that generate keys with NSS should be sufficient. (even starting the browser in FIPS mode and connecting to an SSL website).
Thanks Ales. Here's the test I promised. It turns out the full fipstest.c doesn't build standalone, but I pulled out a simple test to see if this change has been made. Here's what the test looks like in the failure and success conditions:
bobs-laptop(109) cc -o test rngtest.c `pkg-config --cflags --libs nss` -lfreebl
bobs-laptop(109) test
Failed: DRBG initialized without enough entropy
bobs-laptop(110) setenv USE_64 1
bobs-laptop(111) usebuild nss-3-13
bobs-laptop(112) test
Success: DRGB properly failed to initialize without enough entropy.
rngtest.c will be attached in my next post.
bob
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-2011-1584.html