Java SE 7 and JDK 7 Compatibility

For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE (version 7u261) on August 14, 2020. This JRE (version 7u261) will expire with the release of the next critical patch update scheduled for July 14, 2020. For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE (version 7u271) on November 17, 2020. This JRE (version 7u271) will expire with the release of the next critical patch update scheduled for October 20, 2020. For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE (version 7u281) on February 19, 2021.

• Every ObjectInputStream applies a filter, if configured, to the stream contents during deserialization.
• For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE (version 7u231) on November 15, 2019.
• The class file version for Java SE 7 is 51, as per the JVM Specification, because of the invokedynamic byte code introduced by JSR 292.

Accordingly, MD5withRSA has been deactivated by default in the Oracle JSSE implementation by adding “MD5withRSA” to the “jdk.tls.disabledAlgorithms” security property. Now, both TLS handshake messages and X.509 certificates signed with MD5withRSA algorithm are no longer acceptable by default. This change extends the previous MD5-based certificate restriction (“jdk.certpath.disabledAlgorithms”) to also include handshake messages in TLS version 1.2.

Java

Running jarsigner -verify -verbose on a JAR file signed with a weak algorithm or key will print more information about the disabled algorithm or key. To improve the strength of SSL/TLS connections, exportable cipher suites have been disabled in SSL/TLS connections in the JDK by the jdk.tls.disabledAlgorithms Security Property. Clients still may use the no-argument generateSecret method to obtain the raw Diffie-Hellman output, which can be used with an appropriate key derivation function to produce a secret key. 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.

• Users can also deselect the public JRE during the JDK installation and install it separately.
• The keytool’s -importkeystore command is also updated so that it can convert a keystore from one type to another if the source and destination point to the same file.
• This JRE (version 7u95) will expire with the release of the next critical patch update scheduled for April 19, 2016.
• TLS Server certificates issued on or before April 16, 2019 will continue to be trusted until they expire.

To emphasise the point – JDK 7 is the implementation, Java SE 7 is the specification. But everyone at Sun is talking about the JDK (Open JDK), not the specification (Java) and this isn’t an accident. They knew exactly what they were doing by offering a testing kit with a restrictive license.

What is Java JDK?

The keytool and jarsigner tools have been updated to warn users when weak cryptographic algorithms are used in keys, certificates, and signed JARs before they are disabled. The weak algorithms are set in the jdk.security.legacyAlgorithms security property in the java.security configuration file. In this release, the tools issue warnings for the SHA-1 hash algorithm and 1024-bit RSA/DSA keys. The MD5withRSA signature algorithm is now considered insecure and should no longer be used.

• Client-side FTP support in the Java platform is available through the FTP URL stream protocol handler, henceforth referred to as the FTP Client.
• To prevent the use of X.509 certificates that include an MD5-based digital signature algorithm, MD5 has been added to the jdk.certpath.disabledAlgorithms security property.
• The “legacy” key derivation function and its security are unspecified.
• You should be running one of the supported release numbers listed above in the rightmost column.
• If the jdkCA constraint is not set, then all chains using the specified algorithm are restricted.
• This JRE (version 7u251) will expire with the release of the next critical patch update scheduled for April 14, 2020.

The BPR releases are listed below in date order, most current BPR first. Note that bug fixes in previous BPRs are also included in the current BPR. The following sections summarize changes made in all Java SE 7u9 BPR releases. The following sections summarize changes made in all Java SE 7u10 BPR releases. The following sections summarize changes made in all Java SE 7u11 BPR releases. The following sections summarize changes made in all Java SE 7u17 BPR releases.

Java™ Platform Standard Edition 7 Names and Versions

The number “5.0” is used to better reflect the level of maturity, stability, scalability and security of the J2SE. Java 5 was first available on Apple Mac OS X 10.4 (Tiger)[44] and was the default version of Java installed on Apple Mac OS X 10.5 (Leopard). In addition, the string “fb” was removed from java se 7 tutorials the bundle name (the file name of the installer). Web-start applications cannot be launched when clicking JNLP link from IE 11 on Windows 10 Creators Update when 64-bit JRE is installed. If the applet is not ready (the status is not 2), we don’t execute the actual Java method and only return null.

• The following sections summarize changes made in all Java SE 7u211 BPR releases.
• These binaries are provided primarily for use by implementors of
  the Java SE 7 Platform Specification and are recommended for
  reference purposes only.
• For that reason, the JIT compiler has been disabled and it won’t compile any more methods and won’t generate more compiled code.
• The Deployment Toolkit API installLatestJRE() and installJRE(requestedVersion) methods from deployJava.js and the install() method from dtjava.js no longer install the JRE.
• You should compare the checksum of the file you received with the value below to ensure the file you received is complete and unmodified.
• Additional filter patterns can be configured using either a system property or a security property.
• In order to override the JDK system-default parser, applications need to explicitly set the new System property jdk.xml.overrideDefaultParser.