Bug 2228420

Summary:	Enforce EMS in Java in FIPS mode
Product:	Red Hat Enterprise Linux 9	Reporter:	Alexander Sosedkin <asosedki>
Component:	crypto-policies	Assignee:	Alexander Sosedkin <asosedki>
Status:	CLOSED MIGRATED	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.3	CC:	ahughes, fferrari
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	ahughes: needinfo? (fferrari)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-20 00:44:00 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:

Description Alexander Sosedkin 2023-08-02 11:14:19 UTC

I've learned of jdk.tls.allowLegacyMasterSecret=false option's existence.

Should I set it in FIPS mode? What are the downsides?
Which of the JDK versions we ship have this option working?
Will it be simply ignored by those that don't have it working?

Comment 1 Andrew John Hughes 2023-08-03 16:48:08 UTC

I see this property is present in all currently supported JDKs (8, 11, 17).  In all three, it defaults to 'true' (i.e. a legacy master secret is allowed) and indeed, this is unchanged in trunk (future JDK 22).

I've added a NEEDINFO for more information from Francisco who works on the FIPS support. It's not clear to me from this bug why you would want to set this to false. Perhaps I'm missing some context for this bug.

It's also worth noting that this is a system property so it wouldn't currently be controlled by the crypto policies (which this bug is currently filed against). I know we added some support for the crypto policies to list system properties as well, but this is not currently utilised by the JDK support. I'm not sure adding such support is the right direction to go. It would seem preferable to allow the same options to be toggled by security properties as well. I think that might get more traction upstream than trying to override system properties.

Comment 2 RHEL Program Management 2023-09-20 00:42:34 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 3 RHEL Program Management 2023-09-20 00:44:00 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.