Java SE 7 Update 4 Release Notes

On the Linux platform, the names of JRE and JDK packages provided by Java RPM installers have been changed. The names of JRE and JDK packages now follow jre and jdk patterns respectively, instead of jre and jdk previously used. For example, the new names of JRE and JDK packages are jre1.7 and jdk1.7 respectively.

• These cipher suites can be reactivated by removing “DES” from the jdk.tls.disabledAlgorithms security property in the java.security file or by dynamically calling the Security.setProperty() method.
• The PKCS12 KeyStore implementation has been enhanced to support storage of secret keys and trusted certificates.
• In addition, connecting to an HTTP server using SPNEGO usually involves keeping the underlying connection alive and reusing it for further requests to the same server.
• The following sections summarize changes made in all Java SE 7u65 BPR releases.
• Any TLS server certificate chain containing a SHA-1 certificate (end-entity or intermediate CA) and anchored by a root CA certificate included by default in Oracle’s JDK is now blocked by default.
• This JRE (version 7u80) will expire with the release of the next critical patch update scheduled for July 14, 2015.

The limit is the maximum number of interfaces allowed per Proxy in the stream. Setting the limit to zero prevents any Proxies from being deserialized including Annotations, a limit of less than 2 might interfere with RMI operations. A new system https://remotemode.net/ property, jdk.tls.maxCertificateChainLength, has been added to set the maximum allowed length of the certificate chain in TLS/DTLS handshaking. The full version string for this update release is 1.7.0_281-b06 (where “b” means “build”).

Java 11 updates

In addition, the string “fb” was removed from the bundle name (the file name of the installer). This JDK release introduces some changes to how Kerberos requests are handled when a security manager is present. Previously the JDK only supported those currencies listed in table A.1. Not finding the PICL library is a very minor issue, and the warnings mostly lead to confusion. The requirement to have the Authority Key Identifier (AKID) and Subject Key Identifier (SKID) fields matching when building X509 certificate chains has been modified for some cases.

• Additional safeguards to protect against buffer overruns in native code have been enabled on Linux.
• The system property jdk.tls.client.cipherSuites can be used to customize the default enabled cipher suites for the client side of SSL/TLS connections.
• In addition to what John Skeet said, here’s an overview of the Java 7 project.
• This release adds support for automatically showing the touch keyboard for Swing/AWT text components on Microsoft Windows 8 or later.
• The RMI Registry built-in serial filter is modified to check only the array size and not the component type.
• This new system property sets the pool size of the internal DocumentBuilder cache used when processing XML Signatures.

Oracle intends to make future LTS releases every two years meaning the next planned LTS release is Java 25 in September 2025. For the purposes of Oracle Premier Support, non-LTS releases are considered a cumulative set of implementation enhancements of the most recent LTS release. Once a new feature release is made available, any previous non-LTS release will be considered superseded. For example, Java SE 9 was a non-LTS release and immediately superseded by Java SE 10 (also non-LTS), Java SE 10 in turn is immediately superseded by Java SE 11. Java SE 11 however is an LTS release, and therefore Oracle Customers will receive Oracle Premier Support and periodic update releases, even though Java SE 12 was released. The following sections summarize changes made in all Java SE 7u7 BPR releases.

Oracle Java SE Support Roadmap

Please visit java.com/releases for widely distributed releases of Java SE and links to key information about each release. For sandbox app, a second certificate revocation check is always performed after accepting security dialog, ignoring that fact that user already accepted the certificate. If there are network connection problems, such as when a proxy is turned off, the revocation check can take a long time, before java.net.SocketTimeoutException is thrown.

Note that signatures generated using JDK default providers are not affected by this change. TLSv1.2 and TLSv1.1 are now enabled by default on the TLS client end-points. This is similar behavior to what already happens in JDK 8 releases. A new JDK implementation specific system property to control caching for HTTP NTLM connection is introduced.

Java 17 Features (LTS)

This removes the user’s ability during the JDK installation to specify a custom directory in the GUI for the public JRE. If a directory other than the default is desired, use the /INSTALLDIRPUBJRE command-line option to set an installation path for the JRE. Users can also deselect the public JRE during the JDK installation java 7 certifications and install it separately. Moving to Visual Studio 2017 for JDK 7 and JDK 8 requires changing the runtime library that the JDK/JRE depends on. Before this change, JDK/JRE implementations used and shipped the Microsoft Visual C++ 2010 SP1 Redistributable Package (x86/x64) that included MSVCR100.dll [a][b].