Release notes for OpenJDK 11.0.9
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 two versions, OpenJDK 8u and OpenJDK 11u.
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 Container 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.
Chapter 1. Support policy for OpenJDK
Red Hat will support select major versions of OpenJDK in its products. For consistency, these versions will be the same ones that Oracle designates 'LTS' for the Oracle JDK.
A major version of OpenJDK will be supported for a minimum of six years from the time it is first introduced.
OpenJDK 11 is supported on Microsoft Windows and Red Hat Enterprise Linux until October 2024.
RHEL 6 has reached the end of life in November 2020. Due to this, OpenJDK is not supporting RHEL 6 as a supporting configuration.
For more information, see the OpenJDK Life Cycle and Support Policy.
Chapter 2. Differences from upstream OpenJDK 11
OpenJDK in Red Hat Enterprise Linux contains a number of structural changes from the upstream distribution of OpenJDK. The Windows version of OpenJDK tries to follow Red Hat Enterprise Linux as closely as possible.
The most notable changes are the following:
On Red Hat Enterprise Linux, we dynamically link against native libraries such as zlib for archive format support and libjpeg-turbo, libpng, and giflib for image support. Likewise, we dynamically link against Harfzbuzz and Freetype for font rendering and management.
On Microsoft Windows, these libraries are built from the sources of the corresponding Red Hat Enterprise Linux RPMs and packaged as dynamic-link libraries (DLLs).
On Red Hat Enterprise Linux, system-wide timezone data files are used as a source for timezone information.
On Microsoft Windows, the latest available timezone data from Red Hat Enterprise Linux is included.
On Red Hat Enterprise Linux, system-wide CA certificates are used.
On Microsoft Windows, the latest available CA certificate from Red Hat Enterprise Linux is used.
src.zipfile includes the source for all of the JAR libraries shipped with OpenJDK.
Chapter 3. OpenJDK features
3.1. New features and enhancements
This section describes the new features introduced in this release. It also contains information about changes in the existing features.
For all the other changes and security fixes, see https://mail.openjdk.java.net/pipermail/jdk-updates-dev/2020-October/004007.html.
3.1.1. Modified the MS950 charset encoder’s conversion table
Some of the one-way byte-to-char mappings have been aligned with the preferred mappings provided by the Unicode Consortium.
For more information, see JDK-8240196.
3.1.2. Allow SunPKCS11 initialization with NSS when external FIPS modules are present in the Security Modules Database
The SunPKCS11 security provider can now be initialized with NSS when FIPS-enabled external modules are configured in the Security Modules Database (NSSDB). Prior to this change, the SunPKCS11 provider would throw a RuntimeException with the message: "FIPS flag set for non-internal module" when such a library was configured for NSS in non-FIPS mode.
This change allows the OpenJDK to work properly with recent NSS releases in GNU/Linux operating systems when the system-wide FIPS policy is turned on.
For more information, see JDK-8240191.
3.1.3. Localized time zone name inconsistency between English and other locales
English time zone names provided by the CLDR locale provider are now correctly synthesized following the CLDR spec, rather than substituted from the COMPAT provider.
For example, SHORT style names are no longer synthesized abbreviations of LONG style names, but instead produce GMT offset formats.
For more information, see JDK-8238914.
3.1.4. OperatingSystemMXBean methods inside a container return container specific data
When executing in a container, or other virtualized operating environment, the following
OperatingSystemMXBean methods return container-specific information, if available. Otherwise, it returns the following host-specific data:
For more information, see JDK-8236876.
3.1.6. Added 3 SSL Corporation root CA certificates
The following root certificates have been added to the cacerts truststore for the SSL Corporation:
Alias Name: sslrootrsaca
Distinguished Name: CN=SSL.com Root Certification Authority RSA, O=SSL Corporation, L=Houston, ST=Texas, C=US
Alias Name: sslrootevrsaca
Distinguished Name: CN=SSL.com EV Root Certification Authority RSA R2, O=SSL Corporation, L=Houston, ST=Texas, C=US
Alias Name: sslrooteccca
Distinguished Name: CN=SSL.com Root Certification Authority ECC, O=SSL Corporation, L=Houston, ST=Texas, C=US
For more information, see JDK-8250860.
3.1.7. Tools updated to warn users if weak algorithms are used before restricting them
jarsigner tools have been updated to warn users about weak cryptographic algorithms being used before they are disabled. The tools will issue warnings for the SHA-1 hash algorithm and 1024-bit RSA/DSA keys.
For more information, see JDK-8244286.
3.1.8. New system properties to configure the TLS signature scheme
Two new system properties have been added to customize the TLS signature schemes in OpenJDK.
jdk.tls.client.SignatureSchemes has been added for the TLS client side, and
jdk.tls.server.SignatureSchemes has been added for the server side.
Each system property contains a comma-separated list of supported signature scheme names specifying the signature schemes that could be used for the TLS connections.
The names are described in the "Signature Schemes" section of the Java Security Standard Algorithm Names Specification.
For more information, see JDK-8242147.
3.1.9. Support for canonicalize in krb5.conf
The 'canonicalize' flag in the krb5.conf file is now supported by the JDK Kerberos implementation. When set to true, RFC 6806 name canonicalization is requested by clients in TGT requests to KDC services (AS protocol). Otherwise, by default, it is not requested.
The new default behavior is different from previous releases where name canonicalization was always requested by clients in TGT requests to KDC services (provided that support for RFC 6806 was not explicitly disabled with the sun.security.krb5.disableReferrals system or security properties).
For more information, see JDK-8242059.
3.2. Deprecated features
3.2.1. Weak named curves in TLS, CertPath, and Signed JAR disabled by default
Weak named curves are disabled by default by adding them to the following
disabledAlgorithms security properties:
Red Hat has always removed many of the curves provided by upstream, so the only curve disabled in this release is:
The following curves are still enabled:
When large numbers of weak named curves need to be disabled, adding individual named curves to each
disabledAlgorithms property would be overwhelming. To relieve this, a new security property,
jdk.disabled.namedCurves, is implemented that can list the named curves common to all of the
disabledAlgorithms properties. To use the new property in the
disabledAlgorithms properties, precede the full property name with the keyword
include. Users can still add individual named curves to
disabledAlgorithms properties separate from this new property. No other properties can be included in the
To restore the named curves, remove the
include jdk.disabled.namedCurves either from specific or from all
disabledAlgorithms security properties. To restore one or more curves, remove the specific named curve(s) from the
For more information, see JDK-8236730.
3.2.2. US/Pacific-New zone name removed as part of tzdata2020b
The following JDK’s update to tzdata2020b, the long-obsolete files pacificnew and systemv have been removed. As a result, the "US/Pacific-New" zone name declared in the pacificnew data file is no longer available for use.
Information regarding the update can be viewed at https://mm.icann.org/pipermail/tz-announce/2020-October/000059.html
For more information, see JDK-8254177.
Chapter 4. Advisories related to this release
The following advisories have been issued to bugfixes and CVE fixes included in this release.
Revised on 2021-04-22 14:48:58 UTC