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.
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-1.8.0-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-2021:1795
TLS connection randomly fails by exception thrown by P11AEADCipher class (in pkcs11/FIPS mode). It was discovered by ssl-tests [1]. Affected versions: java-1.8.0-openjdk-devel-1.8.0.272.b07-0.1.ea.el8_3 and higher Steps to reproduce: export JAVA_HOME=... make ssl-tests TEST_PKCS11_FIPS=1 SSLTESTS_SSL_CONFIG_FILTER="SunJSSE,Default,TLSv1.2,TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256" SSLTESTS_CUSTOM_JAVA_PARAMS="-Djdk.tls.ephemeralDHKeySize=2048" ... java.lang.RuntimeException: wrong refCount value: -1 at sun.security.pkcs11.NativeKeyHolder.releaseKeyID(P11Key.java:1310) at sun.security.pkcs11.P11Key.releaseKeyID(P11Key.java:152) at sun.security.pkcs11.P11AEADCipher.reset(P11AEADCipher.java:443) at sun.security.pkcs11.P11AEADCipher.implDoFinal(P11AEADCipher.java:708) at sun.security.pkcs11.P11AEADCipher.engineDoFinal(P11AEADCipher.java:538) ... FAILED: SunJSSE/Default: TLSv1.2 + TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256 Where exception in finally block [2] (higher) actually hides PKCS11Exception thrown at: [1] sun.security.pkcs11.P11AEADCipher.cancelOperation (P11AEADCipher.java:344) [2] sun.security.pkcs11.P11AEADCipher.reset (P11AEADCipher.java:440) [3] sun.security.pkcs11.P11AEADCipher.ensureInitialized (P11AEADCipher.java:359) [4] sun.security.pkcs11.P11AEADCipher.implDoFinal (P11AEADCipher.java:639) [5] sun.security.pkcs11.P11AEADCipher.engineDoFinal (P11AEADCipher.java:538) hidde: [1] sun.security.pkcs11.P11AEADCipher.cancelOperation (P11AEADCipher.java:344) [2] sun.security.pkcs11.P11AEADCipher.reset (P11AEADCipher.java:440) [3] sun.security.pkcs11.P11AEADCipher.ensureInitialized (P11AEADCipher.java:359) [4] sun.security.pkcs11.P11AEADCipher.implDoFinal (P11AEADCipher.java:639) [5] sun.security.pkcs11.P11AEADCipher.engineDoFinal (P11AEADCipher.java:538) ... [1] https://github.com/zzambers/ssl-tests [2] https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/file/ebfae7ddcfc1/src/share/classes/sun/security/pkcs11/P11AEADCipher.java#l708