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.

FIPS requires continuous tests of the input to the libraries CSPRNG but the kernel getrandom() (or /dev[u]random) interface does not do it.

Available options is to implement tests in the library or use the kernel AF_ALG DRBG source which wil have these tests implemented in kernel.

Updating the comment to make it more clear to developers what need the CSPRNG check. NSS's PRNG already has a continous random number check. The issue is NSS gets it's seeding from the kernel, which only does the check when the AF_ALG DRBG flag is set.

The latter is preferable, because doing the check in NSS on the random output won't detect a stuck PRNG if NSS doesn't get data in the blocksize of the underlying kernel PRNG.

bob

What the bug is asking is to either keep using the current interfaces as a source of random but add checks in the code that no two consecutive values repeat, or to change NSS to use the kernel AF_ALG interface (via libkcrypto or by direct access) instead as a source of random, because the kernel's interface will have checks there.