|Test the version of Java your browser is using|
Feb 12, 2014: On the Feb 11th edition of Steve Gibsons Security Now podcast he reported that a clean installation of Java 7 Update 51 on Windows disabled Java in all browsers system wide. This is not true. A clean install picks up prior configuration settings left over by previously installed copies of Java. It will also pick up previously whitelisted websites.
Jan 27, 2014: Java 7 Update 51 changed the default security rules for Java and it caught many people by surprise. I mention this because the new security rules prevent the tester applet on this site from running. A longer explanation is on the Version page.
Jan 14, 2014: Oracle updated Java 7 from Update 45 to Update 51 today. This update fixes the usual, disgracefully high, number of bugs (36 or so). Get the latest version at java.com/en/download/manual.jsp to avoid add-on software such as Ask.com.
Dec 10, 2013: Firefox version 26, now blocks Java by default, which puts it on par with Chrome. The hassle factor of running Java in a browser keeps getting higher. Java is fine for use with installed applications, but its use in web browsers has no future. To run a Java applet in a web browser, this first has to be allowed system-wide in the Java Control Panel, then Java security levels need to be dealt with to permit different types of applets, then Firefox and Chrome warn about Java being dangerous and finally Java itself warns about it being dangerous. Firefox puts out two warnings for each applet. Java warnings are worded in such a way as to be confusing. Want fewer messages? Java, Chrome and Firefox each keep separate whitelists of sites allowed to run Java. Is this a Marx Brothers movie?
Nov. 2, 2013: Mozilla is working on changing Firefox to block Java by default. A couple articles written Oct 22nd said this was introduced with Firefox v24 but this is not true. People hate the specific way Firefox implemented this, saying the user interface was too confusing.
Oct. 17, 2013: OS X Snow Leopard (10.6) clarification: I have seen it reported twice on websites with many readers that Apple does not allow Java 6 to run applets (Java programs embedded in web pages, such as the Version page on this site). This is not true on OS X 10.6. It is true on OS X 10.7 and 10.8. I have personally verified that Java 6 Update 65 runs applets just fine on Snow Leopard.
Oct. 15, 2013: Bug fixes released today for Java 7 from Oracle and Java 6 from Apple. The new Java 7 from Oracle, Update 45, fixes 51 bugs. It runs on Windows, Linux and OS X v10.7.3 and above. It is set to expire on Feb. 14, 2014. Oracle also released Java 6 Update 65, but only to their customers with extended support (paid) contracts. Apple today released Java 6 Update 65 (see About the security content of Java for OS X 2013-005 and Mac OS X v10.6 Update 17), which runs on OS X Snow Leopard 10.6.8, Lion 10.7, and Mountain Lion 10.8.
Sept. 11, 2013: Oracle released a new version of Java 7, Update 40 with a huge amount of bug fixes. The new version runs on Windows, Linux and OS X v10.7.3 and above. It is set to expire on Dec. 10, 2013.
Java is supported on Windows, OS X and Linux. It is not supported in iOS or Chrome OS. Java is very much involved in Android, but not in a way that is visible to end users.
Java is used both online and offline in Windows, OS X and Linux. The online use involves Java programs, typically referred to as "applets", embedded in a web page. All the security issues regarding Java involve applets. Offline, Java is used by applications installed in your operating system. Examples of these applications are below in the "Do you need Java" section. The topic of Java being used in a web browser vs. an installed application was addressed by Steve Gibson on the Jan 16, 2013 edition of his Security Now podcast (do a find for "Jared").
A component of Java has to be installed on a computer before Java programs can execute, either online or offline. This component has a couple names. It was initially referred to as the Java Virtual Machine (JVM), but now the more common term is JRE (Java Runtime Environment). Sometimes, it is just referred to as Java, which is a big misnomer as there are many parts to the Java ecosystem.
The latest edition of Java is version 7. It comes from Oracle and is supported on Windows, OS X and Linux. Oracle gave up issuing bug fixes for Java version 6 in the middle of 2013 (for free that is; you can pay Oracle for Java 6 bug fixes). Apple continues to issues bug fixes for Java 6 on Snow Leopard, Lion and Mountain Lion.
On Windows, the Java runtime (JRE) may or may not be pre-installed, the decision is left up to the hardware manufacturer. A Java version 6 runtime was pre-installed by Apple on OS X Leopard and Snow Leopard, but starting with Lion, Apple stopped pre-installing Java. Java 6 can be installed on Lion and Mountain Lion, but it will not run applets. Java 7 can be installed on Lion and Mountain Lion to run applets. Java 7 can not be installed on Snow Leopard. Lion and Mountain can have both Java 6 and Java 7 installed concurrently.
The Java runtime (JRE) on Windows comes from Oracle (previously from Sun). On OS X, Apple supplies the JRE for Java version 6, while Oracle supplies the JRE for Java version 7. Oracle is the official supplier of the JRE for Linux, but there are also other sources available. Microsoft used to maintain their own JRE on Windows but that fell by the wayside long ago. In the old days Netscape had their own JRE as did IBM and others.
Just because a Java runtime is installed, does not mean that a web browser will actually use it. There are three possible reasons for this:
Currently Java has a poor reputation for an endless stream of security flaws. But well before this, Apple and Microsoft did not like Java because it made their operating systems less important. A Java program can, in theory, run equally well on Windows, OS X and Linux. And, that's just for starters. As long as there is a JRE for an operating system, Java programs can run on that system. This opens up other environments too, such as IBM mainframes and Unix. The popular phrase, in the early days of Java was "write once, run anywhere". But, it all went wrong, well before security flaws became the main Java story.
As it played out over the years, Flash beat out Java in the marketplace on the client side (your computer). Flash served the same cross platform needs that Java was intended for. There were annoying differences between Java runtimes from different vendors which led to the sarcastic phrase "write once, debug everywhere." It may be that Flash won out simply because there was only one source (Adobe now, Macromedia initially) for its runtime environment. On the server side however, Java has always been popular.
Java programs are prepared for execution in the JVM/JRE by being translated into something called Java bytecode. The Java Runtime Environment doesn't really care about, or deal with, the Java programming language, it takes Java bytecode as input. This, along with assorted advantages to using a JVM, has led to other programming languages also being translated into Java bytecode so that they can be run in a Java Virtual Machine. In Sept. 2013 Wired reported on two such popular languages, Clojure and Scala. A version of Ruby known as JRuby also runs in a JVM. Wired reported that Twitter runs entirely inside JVMs mostly using software written in Scala but also some written in Java. LinkedIn is also married to JVMs and uses a mixture of Java and Scala.
Now that security flaws are the big issue with Java, the safest best practice is to un-install Java and see if anything breaks. I say this because, as far as I know, there is no inventory function that reports on Java usage system-wide. Since all the security issues have been with Java applets embedded in web pages, someone that only needs Java for installed applications, should disable its use in all browsers using a security feature first introduced in Java 7 Update 10 (see Oracle"s instructions). Someone needing to run Java applets should normally use a web browser that has Java disabled and use a second browser, with Java enabled, exclusively on the site(s) that need Java. If you are not sure which sites use Java, Google's Chrome browser is your friend, as it warns before running Java applets.
The Version page of this site verifies that a browser is capable of running Java applets in web pages by running a very simple applet that displays the version of Java. It also has a history of Java releases and instructions for disabling Java in assorted browsers. The source code for the applet is on the About page.
Java applets can, optionally, be digitally signed. Those that are not, started generating a new pop-up warning with the introduction of Java 7 Update 11. The "version" applet on this site is not signed. Neither is the one at time.gov or those from Oracle that test if Java is working (here and here). The Secunia Online Software Inspector applet is signed.
Finally, you may see Oracle mention the Java security baseline. This refers to the latest version of Java that contains no security flaws. This is not necessarily the latest version. There is a different security baseline edition for Java 6 and 7. To illustrate, as of mid-January 2013, Update 37 was the security baseline edition for Java 6. Windows users had access to Update 38 which contained bug fixes, but no security related bug fixes. Apple did not produce an Update 38 for the Mac, they maxed out at Update 37.
In April 2012, Ed Bott adressed this by listing some applications and websites that require Java. See How big a security risk is Java? Can you really quit using it?. Some omissions from the article are
On the other hand, Libre Office which says it needs Java, in fact, it says so multiple times, seems to run fine without it.
In the beginning, Java programs embedded in web pages were called applets. That's the term I use on this site because it was created long ago. Now however, things are more complicated. According to Oracle, Java programs running inside a browser "includes plugin applets, Java Web Start applications, embedded JavaFX applications, and access to the native deployment toolkit plugins".
Windows users may find the term applet used to describe the small applications in the Control Panel (Power Options, Mouse options, Administrative Tools, etc.). These control panel thingies have nothing to do with Java, other than the Java one, which is referred to as the Java Control Panel.
Java applets can be digitally signed. Those that are not are referred to as "unsigned", "untrusted" and "sandboxed".