Chapter 3. Red Hat build of OpenJDK features
The latest Red Hat build of OpenJDK 11 release might include new features. Additionally, this latest release might enhance, deprecate, or remove features that originated from previous Red Hat build of OpenJDK 11 releases.
For all the other changes and security fixes, see OpenJDK 11.0.15 Released.
3.1. Red Hat build of OpenJDK new features and enhancements Copy linkLink copied to clipboard!
Review the following release notes to understand new features and feature enhancements that have been included with the Red Hat build of OpenJDK 11.0.15 release:
SunPKCS11 provider supports new cipher and keygenerator
The SunPKCS11 provider now supports the following services and algorithms when the PKCS11 library supports the related PKCS#11 mechanism:
If the PKCS11 library supports the CKM_CHACHA20_KEY_GEN mechanism:
- ChaCha20 KeyGenerator
If the PKCS11 library supports the CKM_CHACHA20_POLY1305 mechanism:
- ChaCha20-Poly1305 Cipher
- ChaCha20-Poly1305 AlgorithmParameters
- ChaCha20 SecretKeyFactory
JDK-8255410 contains more information.
Alternative Data Streams (ADS) behavior on Red Hat build of OpenJDK for Microsoft Windows
The Red Hat build of OpenJDK 11 for Microsoft Windows release fixes an issue where some Java applications failed because java.io.FileOutputStream would not open some files containing a colon (:) character. This issue occurred because the default value for jdk.io.File.enableADS was set to false.
This Red Hat build of OpenJDK 11 for Microsoft Windows release sets the default value for the jdk.io.File.enableADS to true. By default, Red Hat build of OpenJDK can now write to Alternative Data Streams and to special files in Microsoft Windows, such as the NUL: file.
You can disable Red Hat build of OpenJDK’s capability to write to ADS by choosing one of the following options:
-
Pass the
-Djdk.io.File.enableADS=falseparameter to your Red Hat build of OpenJDK deployment. -
Set the
JAVA_TOOL_OPTIONSenvironment variable toJAVA_TOOL_OPTIONS=-Djdk.io.File.enableADS=false.
Implementing one of these settings might cause issues with how your Java applications write data into files for your Red Hat build of OpenJDK 11 for Microsoft Windows build.