Bug 2096117

Summary:	SunEC runtime permission for FIPS [rhel-9, openjdk-17]
Product:	Red Hat Enterprise Linux 9	Reporter:	Andrew John Hughes <ahughes>
Component:	java-17-openjdk	Assignee:	Martin Balao <mbalao>
Status:	CLOSED ERRATA	QA Contact:	OpenJDK QA <java-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	fferrari, jandrlik, jvanek
Target Milestone:	rc	Keywords:	Triaged, ZStream
Target Release:	---	Flags:	ahughes: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	java-17-openjdk-17.0.3.0.7-2.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2107941 (view as bug list)		Environment:
Last Closed:	2022-11-15 10:01:35 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:	2107941

Description Andrew John Hughes 2022-06-12 23:35:06 UTC

This bug was initially created as a copy of Bug #2094027

I am copying this bug because: 

FIPS support in RHEL 9 needs to be kept in sync with RHEL 8.

The module jdk.crypto.ec is not granted permission to access the package jdk.internal.access in java.base (java.lang.RuntimePermission "accessClassInPackage.jdk.internal.access"). Under the presence of a Security Manager, any such access throws a security exception. The reason why jdk.crypto.ec needs access is legitimate: determining if OpenJDK is configured in FIPS mode. A similar bug involving the module jdk.crypto.cryptoki has been fixed before [1].

The patch to fix this issue has been authored by @Severin Gehwolf and successfully tested after inclusion in portable builds of java-17-openjdk [2].

--
[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1996182
[2] - http://pkgs.devel.redhat.com/cgit/rpms/java-17-openjdk/commit/java-17-openjdk.spec?h=openjdk-portable-rhel-7&id=d8ffcb9d1ae06c139786858b114bd19c9359220e

Comment 8 errata-xmlrpc 2022-11-15 10:01:35 UTC

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 (java-17-openjdk bug fix and enhancement update), 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-2022:6709