Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 2. Eclipse Temurin features
Eclipse Temurin does not contain structural changes from the upstream distribution of OpenJDK.
For the list of changes and security fixes that the latest OpenJDK 17 release of Eclipse Temurin includes, see OpenJDK 17.0.11 Released.
New features and enhancements
Review the following release notes to understand new features and feature enhancements included with the Eclipse Temurin 17.0.11 release:
XML Security for Java updated to Apache Santuario 3.0.3
In 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 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 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 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
See JDK-8321408 (JDK Bug System).
Revised on 2024-04-26 14:11:06 UTC
