Release notes for Red Hat build of OpenJDK 17.0.11
Abstract
Preface Copy linkLink copied to clipboard!
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 four versions: 8u, 11u, 17u, and 21u.
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 Copy linkLink copied to clipboard!
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
- Click the following link to create a ticket.
- Enter a brief description of the issue in the Summary.
- Provide a detailed description of the issue or enhancement in the Description. Include a URL to where the issue occurs in the documentation.
- Clicking Submit creates and routes the issue to the appropriate documentation team.
Making open source more inclusive Copy linkLink copied to clipboard!
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 Copy linkLink copied to clipboard!
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 Copy linkLink copied to clipboard!
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 andlibjpeg-turbo,libpng, andgiflibfor image support. RHEL also dynamically links againstHarfbuzzandFreetypefor font rendering and management. This change does not apply to Red Hat build of OpenJDK builds for Microsoft Windows. -
The
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 Copy linkLink copied to clipboard!
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 OpenJDK 17.0.11 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.
XML Security for Java updated to Apache Santuario 3.0.3
In Red Hat build of OpenJDK 17.0.11, the XML signature implementation is based on Apache Santuario 3.0.3.
This enhancement introduces the following four SHA-3-based RSA-MGF1 SignatureMethod algorithms:
-
SHA3_224_RSA_MGF1 -
SHA3_256_RSA_MGF1 -
SHA3_384_RSA_MGF1 -
SHA3_512_RSA_MGF1
Because the javax.xml.crypto.dsig.SignatureMethod API cannot be modified in update releases to provide constant values for the new algorithms, use the following equivalent string literal values for these algorithms:
-
http://www.w3.org/2007/05/xmldsig-more#sha3-224-rsa-MGF1 -
http://www.w3.org/2007/05/xmldsig-more#sha3-256-rsa-MGF1 -
http://www.w3.org/2007/05/xmldsig-more#sha3-384-rsa-MGF1 -
http://www.w3.org/2007/05/xmldsig-more#sha3-512-rsa-MGF1
This enhancement also introduces support for the ED25519 and ED448 elliptic curve algorithms, which are both Edwards-curve Digital Signature Algorithm (EdDSA) signature schemes.
In contrast to the upstream community version of Apache Santuario 3.0.3, the JDK still supports the here() function. However, future support for the here() function is not guaranteed. You should avoid using here() in new XML signatures. You should also update any XML signatures that currently use here() to stop using this function. The here() function is enabled by default. To disable the here() function, ensure that the jdk.xml.dsig.hereFunctionSupported system property is set to false.
See JDK-8319124 (JDK Bug System).
Fixed indefinite hanging of jspawnhelper
In earlier releases, if the parent JVM process failed before successful completion of the handshake between the JVM and a jspawnhelper process, the jspawnhelper process could remain unresponsive indefinitely.
In Red Hat build of OpenJDK 17.0.11, if the parent process fails prematurely, the jspawnhelper process receives an end-of-file (EOF) signal from the communication pipe. This enhancement helps to ensure that the jspawnhelper process shuts down correctly.
See JDK-8307990 (JDK Bug System).
SystemTray.isSupported() method returns false on most Linux desktops
In Red Hat build of OpenJDK 17.0.11, the java.awt.SystemTray.isSupported() method returns false on systems that do not support the SystemTray API correctly. This enhancement is in accordance with the SystemTray API specification.
The SystemTray API is used to interact with the taskbar in the system desktop to provide notifications. SystemTray might also include an icon representing an application. Due to an underlying platform issue, GNOME desktop support for taskbar icons has not worked correctly for several years. This platform issue affects the JDK’s ability to provide SystemTray support on GNOME desktops. This issue typically affects systems that use GNOME Shell 44 or earlier.
Because the lack of correct SystemTray support is a long-standing issue on some systems, this API enhancement to return false on affected systems is likely to have a minimal impact on users.
See JDK-8322750 (JDK Bug System).
Certainly R1 and E1 root certificates added
In Red Hat build of OpenJDK 17.0.11, the cacerts truststore includes two Certainly root certificates:
- Certificate 1
- Name: Certainly
- Alias name: certainlyrootr1
- Distinguished name: CN=Certainly Root R1, O=Certainly, C=US
- Certificate 2
- Name: Certainly
- Alias name: certainlyroote1
- Distinguished name: CN=Certainly Root E1, O=Certainly, C=US
Chapter 4. Advisories related to this release Copy linkLink copied to clipboard!
The following advisories are issued to document bug fixes and CVE fixes included in this release:
Revised on 2024-04-19 15:07:32 UTC