- #Java se 6 runtime mac security how to#
- #Java se 6 runtime mac security install#
- #Java se 6 runtime mac security update#
- #Java se 6 runtime mac security full#
The full Java environment is installed, not just a new plug-in. If you do that, it means that you are an expert user who expects to do development in Java 7. Some users who expect to do development using Oracle's Java 7 may instead download the Java Development Kit (JDK). That's also a confirmation of the test page above. You can navigate to the "Java" tab in the middle and see the version.
#Java se 6 runtime mac security update#
When you update to Oracle's latest version, using the link above, you'll also see a new Preference Pane in System Preferences. And if it's not there, you probably don't need it unless you're doing development. That page serves as a test page, to verify your Java plug-in version and also download a new version if required.Įssentially, any previous installation of the full Java 6 Runtime Environment (JRE) from Apple is unaffected.
#Java se 6 runtime mac security how to#
(That plug-in is in /Library/Internet Plug-ins.) It knows how to run Java applets on its own now because buried inside it is a new JRE, build 1.7.0_11-b21) Here is the page where you can do that.
When you visit a specific Oracle webpage to update to the latest version of Java 7, in response to the security alert, you'll be updating your Java Plug-in only.
Unless you know you need to run Java for a specific application, you have no need to do that.
#Java se 6 runtime mac security install#
Mountain Lion doesn't come installed with Java, so if you enter that command, you'll get an invite to install Apple's last integrated version, Java 6. When you enter "java -version" on the terminal line, you're likely to be pointing to the Java 6 previously installed by you (or a Java product) and also used by the developer on his Mac to build the Java app. Also, those apps need to find and use the Java Runtime Environment (JRE), and almost all have been written for Java 6. On the other hand, specialized Java apps written for your Mac, such as Crash Plan would not be affected because they run, stand-alone, not via a browser and Java plug-in. In order to prevent that, on January 10, Apple used its Xprotect mechanism, updated remotely, to prevent the Java plug-in from working if an older version of Java were installed. That became a potential problem (though Oracle originally reported that the exploit only affected Java 7, not Java 6). What's the linkage there? The Java plug-in pointed to Apple's Java 6 JRE. As a result, you'd only have to worry if you visited one of the maliciously crafted websites with an previous version of the Java JRE. The security vulnerability recently reported was exploited by the use of a Java applet, delivered by a malicious website, that runs in your browser. Historically, Java "N" is numbered as 1.N, so if you see "1.6" in the version number, that's Java 6. This, however, doesn't necessarily tell you what version of the Java Runtime Environment (JRE) is installed, and that's what's of interest when discussing this latest exploit.īy the way, the Java numbering scheme is somewhat odd. you will see the version of Java that's installed for local Java applications (like CrashPlan) to use. If you type this terminal command: java -version Previously, the question was whether Java was even installed. So the last version of Java that Apple has integrated into OS X is Java 6. In 2012, Oracle agreed to assume responsibility for Java, starting with Java 7. Very briefly, what you need to know is that, historically, Apple had always integrated Java into its Macs for developers and users. Here's what you need to know in terms of making sure your Mac is secure, how to verify that your update worked, and how to make sure native Java apps developed for Java 6 will still work. The recent Java security update has some minor implications for the average Mac user.