Refer: https://www.oracle.com/java/technologies/javase/8u451-relnotes.html#R180_451

Refer: https://www.oracle.com/java/technologies/javase/8all-relnotes.html#R8u441

Refer -https://www.oracle.com/java/technologies/javase/8u431-relnotes.html#R180_431

Refer - https://www.oracle.com/java/technologies/javase/8u421-relnotes.html#R180_421

Refer - https://www.oracle.com/java/technologies/javase/8u411-relnotes.html#R180_411

Refer - https://www.oracle.com/java/technologies/javase/8u401-relnotes.html#R180_401

Refer -https://www.oracle.com/java/technologies/javase/8u391-relnotes.html#R180_391

Refer -https://www.oracle.com/java/technologies/javase/8u371-relnotes.html

New Features$$$security-libs/java.security$$$? Support for RSASSA-PSS in OCSP Response (JDK-8274471)$$$An OCSP response signed with the RSASSA-PSS algorithm is now supported.

New Features$$$security-libs/java.security$$$? Upgrade the Default PKCS12 MAC Algorithm (JDK-8267880)$$$The default MAC algorithm used in a PKCS #12 keystore has been updated. The new algorithm is based on SHA-256 and is stronger than the old one based on SHA-1. See the security properties starting with keystore.pkcs12 in the java.security file for detailed information.$$$$$$The new SHA-256 based MAC algorithms were introduced in the 11.0.12; 8u301; and 7u311 JDK versions. Keystores created using this newer; stronger; MAC algorithm cannot be opened in JDK versions earlier than 11.0.12; 8u301; and 7u311. A java.security.NoSuchAlgorithmException exception will be thrown in such circumstances.$$$$$$For compatibility; use the keystore.pkcs12.legacy system property; which will revert the algorithms to use the older; weaker algorithms. There is no value defined for this property.$$$$$$hotspot/runtime$$$? os::set_native_thread_name() cleanups (JDK-7102541)$$$On platforms that support the concept of a thread name on their native threads; the java.lang.Thread.setName() method will also set that native thread name. However; this will only occur when called by the current thread; and only for threads started through the java.lang.Thread class (not for native threads that have attached via JNI). The presence of a native thread name can be useful for debugging and monitoring purposes. Some platforms may limit the native thread name to a length much shorter than that used by the java.lang.Thread; which may result in some threads having the same native name.$$$$$$Refer-https://www.oracle.com/java/technologies/javase/8u-relnotes.html