In JDK 7u51, users are given an option to restore the security prompts, for any prompts that were hidden prior to installing the latest release. The Jarsigner tool will print out an informational warning at signing or verifying when timestamp is missing. Please visit java.com/releases for widely distributed releases of Java SE and links to key information about each release. Note that if the name service is not trustworthy, enabling reverse name lookup may be susceptible to MITM attacks. This JDK release introduces some changes to how Kerberos requests are handled when a security manager is present. The dns_lookup_realm setting in Kerberos’ krb5.conf file is by default false.
The jdk.tls.client.protocols system property is now available with the release of JDK 7u95. This property was originally introduced in JDK 8 and behaves in the same way. All our BPR releases are configured with Java Auto Update disabled as default unless otherwise mentioned. This enhancement provides a way to specify more granular levels for the GC verification enabled using the VerifyBeforeGC, VerifyAfterGC, and VerifyDuringGC diagnostic options. It introduces a new diagnostic option VerifySubSet with which one can specify the subset of the memory system that should be verified. The Deployment Toolkit API installLatestJRE() and installJRE(requestedVersion) methods from deployJava.js and the install() method from dtjava.js no longer install the JRE.
The language is specified by the Java Language Specification (JLS); changes to the JLS are managed under JSR 901. The java.net.ExtendedSocketOptions TCP_KEEPIDLE and TCP_KEEPINTERVAL are supported on Windows platforms starting from Windows 10 version 1709 and onwards. TCP_KEEPCOUNT is supported starting from Windows 10 version 1703 and onwards.
Please note that fixes from prior BPR (7u141 b33) are included in this version. If an application requires a Java SE 6 or 7 JRE, the Java Deployment technology in JRE 8 release can be used to run such applications. Keep the backup copy of the keystore at least until you are sure the imported keystore is correct. Please note that fixes from prior BPR (7u151 b33) are included in this version. The overrideDefaultParser property can be set through the System.setProperty.
These cipher suites can still be enabled by SSLEngine.setEnabledCipherSuites() and SSLSocket.setEnabledCipherSuites() methods. This release also contains fixes for security vulnerabilities described in the Oracle Java SE Critical Patch Update Advisory. For a more complete list java 7 certifications of the bug fixes included in this release, see the JDK 7u111 Bug Fixes page. For a more complete list of the bug fixes included in this release, see the JDK 7u121 Bug Fixes page. In some environments certain authentication schemes may be undesirable when proxying HTTPS.
For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE (version 7u71) on February 20, 2015. After either condition is met (new release becoming available or expiration date reached), the JRE will provide additional warnings and reminders to users to update to the newer version. For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE (version 7u51) on May 15, 2014.
Explicitly setting enabled cipher suites will override the system properties. 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 a similar way, the system property jdk.tls.server.cipherSuites can be used for customization on the server side.
JDK 7u71 (CPU) contains vulnerability fixes and JDK 7u72 (PSU) contains all of the fixes from 7u71 plus some additional non-critical stability fixes. An issue with the Mac OS X poll(2) system call has been found to cause problems for networking applications based on the java.nio socket channel classes. This issue has been detected with the Oracle WebLogic Server on Mac OS X. In the current JDK release, wildcards in quoted arguments get expanded, and the matched file names (.java) are passed to xxx.
Version numbers are commonly used for marketing and documentation purposes. Other proprietary Java implementations are available, such as Azul’s Zing. Azul offers certified open source OpenJDK builds under the Zulu moniker.
