Bug 2134669

Summary:	Add missing attributes when registering services in FIPS mode [rhel-8, openjdk-17]
Product:	Red Hat Enterprise Linux 8	Reporter:	Martin Balao <mbalao>
Component:	java-17-openjdk	Assignee:	Martin Balao <mbalao>
Status:	CLOSED MIGRATED	QA Contact:	OpenJDK QA <java-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	8.7	CC:	ahughes, fferrari, jvanek
Target Milestone:	rc	Keywords:	MigratedToJIRA, Reopened, Triaged, ZStream
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	java-17-openjdk-17.0.7.0.7-3.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2186834 2186835 2186836 2186837 (view as bug list)		Environment:
Last Closed:	2024-05-10 23:49:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2156945, 2186834, 2186835, 2186836, 2186837

Description Martin Balao 2022-10-14 01:09:55 UTC

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 8 RHEL Program Management 2024-05-10 23:43:59 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 9 RHEL Program Management 2024-05-10 23:49:02 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.