Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

What's new with Java

Michael Horowitz | Nov. 3, 2014
There are three latest versions of Java. Tweaking Java to disable SSL 3.0. Securing Java. Explaining the security messages when running Java applets. Expiring old versions of Java.

But, this does not work.

I was able to run the unsigned applet on my site, on Windows 7, with both Java 7 and 8. I tested with Firefox 33 and Chrome 38.

Sometimes these things need a re-boot before kicking in, but that wasn't the case here. After restarting Windows, my applet was still able to run.

Way to go Oracle.

In December 2012 Oracle introduced the concept of the Java runtime (a.k.a. JRE and JVM) expiring. As a security measure, each version since Java 7 Update 10 has had an expiration date. Actually, two dates.

The shorter expiration date is roughly three months after the Java Update was released. However, computers that can not phone home to Oracle, have their versions of Java expire in four months.

As Oracle describes this

The "additional protection" is, yet another, warning message.

Java 7 Update 60 was scheduled to expire on July 15, 2014 if it could phone home, and on August 15, 2014 if it could not. Despite this, in October 2014 I was able to run an unsigned applet on a Windows system with Update 60 installed (the security level was "high").

As shown below, there was a warning about Java being "out of date" but the applet ran nonetheless.

The best thing about iOS, Android and Chrome OS may be that they don't support the use of Java inside a web browser.  


Previous Page  1  2  3  4 

Sign up for CIO Asia eNewsletters.