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.
Bug 2094027 - SunEC runtime permission for FIPS [rhel-8, openjdk-17]
Summary: SunEC runtime permission for FIPS [rhel-8, openjdk-17]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: java-17-openjdk
Version: 8.6
Hardware: All
OS: All
unspecified
low
Target Milestone: rc
: ---
Assignee: Martin Balao
QA Contact: OpenJDK QA
URL:
Whiteboard:
Depends On:
Blocks: 2108209 2108210 2128101 2129199 2156945
TreeView+ depends on / blocked
 
Reported: 2022-06-06 15:36 UTC by Martin Balao
Modified: 2022-12-29 20:46 UTC (History)
5 users (show)

Fixed In Version: java-17-openjdk-17.0.3.0.7-2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2108209 2108210 2128101 (view as bug list)
Environment:
Last Closed: 2022-11-08 09:30:31 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rh-openjdk jdk pull 5 0 None Merged RH2094027: SunEC runtime permission for FIPS 2022-10-14 16:24:46 UTC
Red Hat Issue Tracker RHELPLAN-124380 0 None None None 2022-06-06 15:41:05 UTC
Red Hat Product Errata RHBA-2022:6691 0 None None None 2022-11-08 09:31:34 UTC

Description Martin Balao 2022-06-06 15:36:46 UTC
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 1 Martin Balao 2022-06-06 17:36:42 UTC
PR: https://github.com/rh-openjdk/jdk/pull/5

Comment 2 Martin Balao 2022-06-08 19:15:38 UTC
The PR has been merged here: https://github.com/rh-openjdk/jdk/commit/da9988cfccc9c974a917c8540bd5aac04197b046

Comment 10 errata-xmlrpc 2022-11-08 09:30:31 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:6691


Note You need to log in before you can comment on or make changes to this bug.