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.
This bug was initially created as a copy of Bug #2134669
When OpenJDK is in FIPS mode, the list of services and algorithms that security providers are allowed to register is limited. As an example, we don't allow the non-FIPS compliant SUN security provider to register the Signature service for any of its algorithms. The reason for this algorithms and services lockdown is that we don't want non-FIPS compliant crypto to be inadvertently used. This could happen if an application requires an algorithm for which the FIPS-compliant security provider (SunPKCS11) does not have an implementation and a non-FIPS compliant security provider does. Notice that the priority ordering of security providers cannot prevent this scenario.
On the other hand, services which don't imply cryptographic operations might need to be allowed in FIPS mode. As an example, we need the `AlgorithmParameters` service for the DSA algorithms from SUN to be available.
RH2052070 is an example of a patch that implemented this scheme.
Services registration might involve string attributes that can later be used to get a filtered selection of the security providers available, using the `java.security.Security::getProviders(Map<String,String> filter)` public API.
The same global dictionary of attributes is used for different service registrations; with attributes added, removed or cleared as needed. The way in which RH2052070 was implemented has a flaw that manifests in FIPS mode: some attributes are missing because they are only added to the dictionary in non-FIPS mode.
This was found in the context of reviewing a backport of RH2052070 to java-11-openjdk: https://github.com/rh-openjdk/jdk11u/pull/5#pullrequestreview-1130703203
We estimate that the impact of this issue is low but we intend to fix it.
Comment 7RHEL Program Management
2023-09-12 23:30:58 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 8RHEL Program Management
2023-09-12 23:31:37 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.