SupportConsoleDevelopersStart a trialContact

Release notes for Red Hat build of OpenJDK 17.0.8

Red Hat build of OpenJDK 17

Red Hat Customer Content Services

Abstract

The Release notes for Red Hat build of OpenJDK 17.0.8 document provides an overview of new features in Red Hat build of OpenJDK 17 and a list of potential known issues and possible workarounds.

Preface

Open Java Development Kit (OpenJDK) is a free and open source implementation of the Java Platform, Standard Edition (Java SE). The Red Hat build of OpenJDK is available in three versions: 8u, 11u, and 17u.

Packages for the Red Hat build of OpenJDK are made available on Red Hat Enterprise Linux and Microsoft Windows and shipped as a JDK and JRE in the Red Hat Ecosystem Catalog.

Providing feedback on Red Hat build of OpenJDK documentation

To report an error or to improve our documentation, log in to your Red Hat Jira account and submit an issue. If you do not have a Red Hat Jira account, then you will be prompted to create an account.

Procedure

  1. Click the following link to create a ticket.
  2. Enter a brief description of the issue in the Summary.
  3. Provide a detailed description of the issue or enhancement in the Description. Include a URL to where the issue occurs in the documentation.
  4. Clicking Submit creates and routes the issue to the appropriate documentation team.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

Chapter 1. Support policy for Red Hat build of OpenJDK

Red Hat will support select major versions of Red Hat build of OpenJDK in its products. For consistency, these versions remain similar to Oracle JDK versions that are designated as long-term support (LTS).

A major version of Red Hat build of OpenJDK will be supported for a minimum of six years from the time that version is first introduced. For more information, see the OpenJDK Life Cycle and Support Policy.

Note

RHEL 6 reached the end of life in November 2020. Because of this, Red Hat build of OpenJDK is not supporting RHEL 6 as a supported configuration..

Chapter 2. Differences from upstream OpenJDK 17

Red Hat build of OpenJDK in Red Hat Enterprise Linux contains a number of structural changes from the upstream distribution of OpenJDK. The Microsoft Windows version of Red Hat build of OpenJDK attempts to follow Red Hat Enterprise Linux updates as closely as possible.

The following list details the most notable Red Hat build of OpenJDK 17 changes:

  • FIPS support. Red Hat build of OpenJDK 17 automatically detects whether RHEL is in FIPS mode and automatically configures Red Hat build of OpenJDK 17 to operate in that mode. This change does not apply to Red Hat build of OpenJDK builds for Microsoft Windows.
  • Cryptographic policy support. Red Hat build of OpenJDK 17 obtains the list of enabled cryptographic algorithms and key size constraints from the RHEL system configuration. These configuration components are used by the Transport Layer Security (TLS) encryption protocol, the certificate path validation, and any signed JARs. You can set different security profiles to balance safety and compatibility. This change does not apply to Red Hat build of OpenJDK builds for Microsoft Windows.
  • Red Hat build of OpenJDK on RHEL dynamically links against native libraries such as zlib for archive format support and libjpeg-turbo, libpng, and giflib for image support. RHEL also dynamically links against Harfbuzz and Freetype for font rendering and management. This change does not apply to Red Hat build of OpenJDK builds for Microsoft Windows.
  • The src.zip file includes the source for all of the JAR libraries shipped with Red Hat build of OpenJDK.
  • Red Hat build of OpenJDK on RHEL uses system-wide timezone data files as a source for timezone information.
  • Red Hat build of OpenJDK on RHEL uses system-wide CA certificates.
  • Red Hat build of OpenJDK on Microsoft Windows includes the latest available timezone data from RHEL.
  • Red Hat build of OpenJDK on Microsoft Windows uses the latest available CA certificate from RHEL.

Additional resources

Chapter 3. Red Hat build of OpenJDK 17.0.8.1 release notes

Review the following release note to understand changes from the Red Hat build of OpenJDK 17.0.8.1 patch release.

Note

For all the other changes and security fixes, see OpenJDK 17.0.8.1 Released.

Fixed Invalid CEN header error on valid .zip files

Red Hat build of OpenJDK 17.0.8 introduced additional validation checks on the ZIP64 fields of .zip files (JDK-8302483). However, these additional checks caused validation failures on some valid .zip files with the following error message: Invalid CEN header (invalid zip64 extra data field size).

To fix this issue, Red Hat build of OpenJDK 17.0.8.1 supports zero-length headers and the additional padding that some ZIP64 creation tools produce. From Red Hat build of OpenJDK 17.0.8 onward, you can disable these checks by setting the jdk.util.zip.disableZip64ExtraFieldValidation system property to true.

See JDK-8313765 (JDK Bug System)

Increased default value of jdk.jar.maxSignatureFileSize system property

Red Hat build of OpenJDK 17.0.8 introduced a jdk.jar.maxSignatureFileSize system property for configuring the maximum number of bytes that are allowed for the signature-related files in a Java archive (JAR) file (JDK-8300596). By default, the jdk.jar.maxSignatureFileSize property was set to 8000000 bytes (8 MB), which was too small for some JAR files.

Red Hat build of OpenJDK 17.0.8.1 increases the default value of the jdk.jar.maxSignatureFileSize property to 16000000 bytes (16 MB).

See JDK-8313216 (JDK Bug System)

The following advisories have been issued to bug fixes and CVE fixes included in this release:

Chapter 4. Red Hat build of OpenJDK features

The latest Red Hat build of OpenJDK 17 release might include new features. Additionally, the latest release might enhance, deprecate, or remove features that originated from previous Red Hat build of OpenJDK 17 releases.

Note

For all the other changes and security fixes, see OpenJDK 17.0.8 Released.

Red Hat build of OpenJDK enhancements

Red Hat build of OpenJDK 17 provides enhancements to features originally created in previous releases of Red Hat build of OpenJDK.

Reduced risk of JVM crash when using GregorianCalendar.computeTime()

In Red Hat build of OpenJDK 17.0.7, a virtual machine crash could occur when using the GregorianCalendar.computeTime() method (JDK-8307683). Even though an old issue is the root cause of this JVM crash, a recent fix for a rare issue in the C2 compiler (JDK-8297951) significantly increased the probability of the JVM crash. To mitigate risk, the Red Hat build of OpenJDK 17.0.8 release excludes the fix for the C2 compiler. Once the root cause of the JVM crash is resolved (JDK-8307683), Red Hat build of OpenJDK will reintroduce the fix for the C2 compiler (JDK-8297951).

See JDK-8308884 (JDK Bug System).

Support for GB18030-2022

The Chinese Electronics Standardization Institute (CESI) recently published GB18030-2022 as an update to the GB18030 standard, synchronizing the character set with Unicode 11.0. The GB18030-2022 standard is now the default GB18030 character set that Red Hat build of OpenJDK 17.0.8 uses. However, this updated character set contains incompatible changes compared with GB18030-2000, which previous releases of Red Hat build of OpenJDK 17 used. From Red Hat build of OpenJDK 17.0.8 onward, if you want to use the previous version of the character set, ensure that the new system property jdk.charset.GB18030 is set to 2000.

See JDK-8301119 (JDK Bug System).

Enhanced ZIP performance

The Red Hat build of OpenJDK 17.0.8 release includes enhanced checks on the ZIP64 fields of .zip files. If these checks cause failures on trusted .zip files, you can disable these checks by setting the new system property jdk.util.zip.disableZip64ExtraFieldValidation to true.

JDK bug system reference ID: JDK-8302483.

Enhanced validation of JAR signature

You can now configure the maximum number of bytes that are allowed for the signature-related files in a Java archive (JAR) file by setting a new system property, jdk.jar.maxSignatureFileSize. By default, the jdk.jar.maxSignatureFileSize property is set to 8000000 bytes (8 MB).

JDK bug system reference ID: JDK-8300596.

GTS root certificate authority (CA) certificates added

In the Red Hat build of OpenJDK 17.0.8 release, the cacerts truststore includes four Google Trust Services (GTS) root certificates:

Certificate 1
  • Name: Google Trust Services LLC
  • Alias name: gtsrootcar1
  • Distinguished name: CN=GTS Root R1, O=Google Trust Services LLC, C=US
Certificate 2
  • Name: Google Trust Services LLC
  • Alias name: gtsrootcar2
  • Distinguished name: CN=GTS Root R2, O=Google Trust Services LLC, C=US
Certificate 3
  • Name: Google Trust Services LLC
  • Alias name: gtsrootcar3
  • Distinguished name: CN=GTS Root R3, O=Google Trust Services LLC, C=US
Certificate 4
  • Name: Google Trust Services LLC
  • Alias name: gtsrootcar4
  • Distinguished name: CN=GTS Root R4, O=Google Trust Services LLC, C=US

See JDK-8307134 (JDK Bug System).

Microsoft Corporation root CA certificates added

In the Red Hat build of OpenJDK 17.0.8 release, the cacerts truststore includes two Microsoft Corporation root certificates:

Certificate 1
  • Name: Microsoft Corporation
  • Alias name: microsoftecc2017
  • Distinguished name: CN=Microsoft ECC Root Certificate Authority 2017, O=Microsoft Corporation, C=US
Certificate 2
  • Name: Microsoft Corporation
  • Alias name: microsoftrsa2017
  • Distinguished name: CN=Microsoft RSA Root Certificate Authority 2017, O=Microsoft Corporation, C=US

See JDK-8304760 (JDK Bug System).

TWCA root CA certificate added

In the Red Hat build of OpenJDK 17.0.8 release, the cacerts truststore includes the Taiwan Certificate Authority (TWCA) root certificate:

  • Name: TWCA
  • Alias name: twcaglobalrootca
  • Distinguished name: CN=TWCA Global Root CA, OU=Root CA, O=TAIWAN-CA, C=TW

See JDK-8305975 (JDK Bug System).

New JFR event jdk.SecurityProviderService

Calls to the java.security.Provider.getService(String type, String algorithm) method now trigger a new JFR event, jdk.SecurityProviderService.

The jdk.SecurityProviderService event contains the following three fields:

  • Type: The type of service
  • Algorithm: The algorithm name
  • Provider: The security provider

The jdk.SecurityProviderService event is disabled by default. You can enable this event by using the standard JFR configuration files and options.

See JDK-8254711 (JDK Bug System).

Chapter 5. Advisories related to this release

The following advisories are issued to document bug fixes and CVE fixes included in this release:

Revised on 2024-05-03 15:37:05 UTC

Legal Notice

Copyright © 2024 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.