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.
Should be easy to do.
Btw I know that in the past Harald was talking to kernel maintainers about moving the list of crypto modules used in FIPS to kernel package. So you know anything about that?
I can't say that I do, no. Was it herbert he was speaking to? We can cc him if need be to get status.
FWIW, The selftest manager in the kernel has a fips_enabled flag for each algorithm allowed in fips mode, which we could export, but thats a list of algorithms, not a list of modules, so I don't know how close that gets you to your goal
Lukas, yes, we understand the testing is pretty straightforward, but this bz is still open, so ostensibly we're still waiting for the work to enabling said loading to be completed. Is that work done, and if so, can you update and close this bz please?
Hello Neil,
I'm trying to verify this bug but I cannot find which module is expected to be loaded. Could you please provide information which module provides the cipher and/or how to detect the cipher is loaded and available.
Thank you
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.
https://access.redhat.com/errata/RHBA-2019:3604