restart disables javaws again

An updated version of Java 1.7 is now available which will run on Mountain Lion:

http://www.oracle.com/technetwork/topics/security/javacpufeb2013-1841061.html

It may run on Mountain Lion but it won't be compatible with the Java application I need it to run with.

You were correct. I had to tweak the JavaComponentMinimumVersion on each machine. I found the right version to use my entering "java -version" in Terminal and looking at the Runtime Environment variable.

That Java application needs to be updated soon as Java 1.6 is disappearing very soon:

http://www.java.com/en/download/faq/java_6.xml

alucasTHX wrote:

Um. Isn't that what I already said?

Yes, I overlooked your more thorough exmaination here: https://discussions.apple.com/thread/4760961?answerId=21097725022#21097725022

"Admittedly, Apple should be a bit more open about what's going on here. However, it's extremely short-sighted to criticize them for trying to keep you safe from threats that you are unaware of. If you don't like security, switch to Windows, where you can keep using Java just fine... assuming the viruses don't cripple your machine, steal your identity and destroy all your important data."

Great thinking! Of course your criticisms of the Windows platform are only accurate if you're still beating up on Windows 98, but hey, I like to drive old muscle cars.

As a network engineer, we call this approach to security/problem solving the Nirvana approach (from their Unplugged album). Its where you don't consult or do any troubleshooting, you just yank out all the wires from the switch and then deal with the calls regarding loss of internet, everything else was the problem and/or those people that don't notice didn't need the interwebs anyway.

Ever wonder why the business community stays away from crApple? Security through obscurity and the heavy handed approach are just two reasons.

Thank you very MUCH!!! Now I'm alive once again!!!!

Not sure what happened, but I'm now getting the Blocked Plug-in again in Safari. I ran the command:

sudo /usr/libexec/PlistBuddy -c "Delete :JavaWebComponentVersionMinimum" /System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/XProtect.meta. plist

But still getting it. So very frustrating. I can't believe Apple is that ignorant to the corporate world where the legacy java apps just won't work with the newest version.

Not sure what happened, but I'm now getting the Blocked Plug-in again in Safari

Yup, they bumped up the blocked version of Java again, following new vulnerabilities that were being actively exploited and a subsequent Java update.

I can't believe Apple is that ignorant to the corporate world where the legacy java apps just won't work with the newest version.

It's the corporate world that is ignorant, in this case. Just using Java in a web browser at all is dangerous, but anyone using legacy versions of Java in a web browser is nuts! If your employer is making you use legacy versions of Java on web sites, you need to do that only on a cheap throwaway netbook, with absolutely no sensitive data on it and that gets used for nothing else, or in a virtual machine running in something like Parallels.

I'm not accessing external java sites. For this particular instance, I'm trying to run Cisco UCS manager. Again, I get the risks, but I don't need Apple force feeding updates down my throat. It's my computer, and I should be able to dictate the versions of software I want to run on it. It's inexcusable that Apple makes these changes mandatory. They absolutely should have an opt out or at the very least, back out option.

Well, I've reverted to using this command and was able to get it working successfully.

sudo defaults write /System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/XProtect.meta JavaWebComponentVersionMinimum "1.6.0_37-b06-434"

There *is* an opt out. Software Update preference pane, uncheck "Install system data files and security updates."

Thank you so much. Never noticed that. Went ahead an unchecked it and hope to avoid these java issues in the future.

So now I'm getting a "Blocked Plug-in" message for attachements in Mail. Sigh, I love how things 'just work'.