Hide Forgot
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.
Created attachment 528908 [details] Update drbg health tests for FIPS
upstream bug
adding exception request. This patch is required for FIPS. bob
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).
Created attachment 529976 [details] Update drbg health, after upstream comments. Elio, go ahead and build with this patch. bob
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
Created attachment 530412 [details] simple test case to see if the new rng tests are in use.
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