Release notes for Red Hat build of OpenJDK 17.0.6
Red Hat build of OpenJDK (Open Java Development Kit) 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.
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.
Providing feedback on Red Hat documentation
We appreciate your feedback on our documentation. To provide feedback, you can highlight the text in a document and add comments.
This section explains how to submit feedback.
- You are logged in to the Red Hat Customer Portal.
- In the Red Hat Customer Portal, view the document in Multi-page HTML format.
To provide your feedback, perform the following steps:
Click the Feedback button in the top-right corner of the document to see existing feedback.Note
The feedback feature is enabled only in the Multi-page HTML format.
- Highlight the section of the document where you want to provide feedback.
Click the Add Feedback pop-up that appears near the highlighted text.
A text box appears in the feedback section on the right side of the page.
Enter your feedback in the text box and click Submit.
A documentation issue is created.
- To view the issue, click the issue tracker link in the feedback view.
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.
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
zlibfor archive format support and
giflibfor image support. RHEL also dynamically links against
Freetypefor font rendering and management. This change does not apply to Red Hat build of OpenJDK builds for Microsoft Windows.
src.zipfile 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.
Chapter 3. 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.
For all the other changes and security fixes, see Red Hat build of OpenJDK 17.0.6 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.
Enhanced BMP bounds
By default, Red Hat build of OpenJDK 17.0.6 disables loading a linked International Color Consortium (ICC) profile in a BMP image. You can enable this functionality by setting the new
sun.imageio.bmp.enabledLinkedProfiles property to
true. This property replaces the old
Improved banking of sounds
com.sun.media.sound.JARSoundbankReader, downloaded a JAR soundbank from a URL. For Red Hat build of OpenJDK 17.0.6, this behavior is now disabled by default. To re-enable the behavior, set the new system property
Enhanced Datagram Transport Layer Security (DTLS) performance
Red Hat build of OpenJDK now exchanges DTLS cookies for all new and resumed handshake communications.
To re-enable the previous release behavior, set the new system property
Added note for
The Red Hat build of OpenJDK 9 release changed the
Set implementation, which holds principals and credentials, so that the implementation can reject
null values. Any attempts to call
remove(null) would throw a
The Red Hat build of OpenJDK 9 release did not update the
logout() method in the
LoginModule implementation to check for
null values. These values could occur because of a failed login attempt, which can cause a
logout() call to throw a
The Red Hat build of OpenJDK 17.0.6 release updates the
LoginModule implementations to check for
null values. Additionally, the release adds an implementation note to the specification that states the change also applies to third-party modules. The note advises developers of third-party modules to verify that a
logout() method does not throw a
Chapter 4. Advisories related to this release
The following advisories have been issued to bugfixes and to CVE fixes included in this release:
Revised on 2023-11-02 17:26:38 UTC