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.
IllegalAccessException by pkcs11 provider:
- triggered when trying to obtain DH private/public keys
- pkcs11 provider tries to create instance of SunJCE provider (placed in java.base module) which causes "Illegal access exception" [1]
- affects only modular jdks (affected: 11, latest-upstream; not affected: 8)
- should be probably easy to fix using "export to" in java.base's module-info [2]
Stack trace:
Exception in thread "main" java.security.ProviderException: Could not find provider SunJCE
at jdk.crypto.cryptoki/sun.security.pkcs11.P11Util.getProvider(P11Util.java:95)
at jdk.crypto.cryptoki/sun.security.pkcs11.P11Util.getSunJceProvider(P11Util.java:76)
at jdk.crypto.cryptoki/sun.security.pkcs11.P11Key$P11DHPublicKey.getEncodedInternal(P11Key.java:952)
at jdk.crypto.cryptoki/sun.security.pkcs11.P11Key.getEncoded(P11Key.java:164)
at IllegalAccess.main(IllegalAccess.java:8)
Caused by: java.lang.IllegalAccessException: class sun.security.pkcs11.P11Util (in module jdk.crypto.cryptoki) cannot access class com.sun.crypto.provider.SunJCE (in module java.base) because module java.base does not export com.sun.crypto.provider to module jdk.crypto.cryptoki
at java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
at java.base/jdk.internal.reflect.Reflection.ensureMemberAccess(Reflection.java:99)
at java.base/java.lang.Class.newInstance(Class.java:579)
at jdk.crypto.cryptoki/sun.security.pkcs11.P11Util.getProvider(P11Util.java:92)
... 4 more
[1] https://hg.openjdk.java.net/jdk-updates/jdk11u/file/030bc020dc04/src/jdk.crypto.cryptoki/share/classes/sun/security/pkcs11/P11Util.java#l71
[2] https://hg.openjdk.java.net/jdk-updates/jdk11u/file/030bc020dc04/src/java.base/share/classes/module-info.java
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-11-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-2020:4657