More Java Patches Due Soon

CommanderFrank

Cat Can't Scratch It
Joined
May 9, 2000
Messages
75,399
Since patching Java SE is such a hoot, Oracle is doing a mid-month encore. It seems in the rush to patch a vulnerability, several needed patches were not included. The good news here is if you skipped the updates on February 1st, everything will be updated at the same time on February 19th.

Oracle has come under fire lately over Java, not only regarding vulnerabilities but also the fact that Java updates include third-party software, or as some critics call it, "crapware," such as the Ask.com toolbar.
 
Actually, the Feb 1st update was the update they planned for the 19th, just released early. The next update is scheduled for June 18 and they'll probably stick to that plan once again unless they get embarrassed again in mainstream news.
 
Actually, the Feb 1st update was the update they planned for the 19th, just released early. The next update is scheduled for June 18 and they'll probably stick to that plan once again unless they get embarrassed again in mainstream news.

"Unless...". LMAO. You're a riot. :D
 
It isn't really funny though. They are just like Adobe was three years ago, want to do updates quarterly, and stick their heads in the sand and claim it's not that serious when major exploits happen. If news of the exploits didn't hit the national news I have no doubt they would insist that sticking to the original 19th date is fine.
 
I uninstalled Java from both my computers a while ago. Haven't missed it. If Java would just auto update without trying to install some sort of crap-ware it wouldn't be so bad.:rolleyes:
 
Has anyone else had problems deploying Java 7 Update 13 via Software Installation in AD? It's been corrupting installs on my test stations. Have never had a problem like this before.
 
Has anyone else had problems deploying Java 7 Update 13 via Software Installation in AD? It's been corrupting installs on my test stations. Have never had a problem like this before.

Welcome to almost every Java update pushed through SCCM. It has a history of breaking operating systems, uninstalling and then installing in a corrupted and broken way, or uninstalling and the previous version and not installing a new one which leaves the system working but in need of a Java install done manually.

Stupid cross-platform programming and stupid on-the-fly code translation. The people who made Java probably never saw it coming, but Sun and now Oracle are horrible for shoveling Java on the world and developers are all dumb poop heads for compiling junk in Java.
 
Welcome to almost every Java update pushed through SCCM. It has a history of breaking operating systems, uninstalling and then installing in a corrupted and broken way, or uninstalling and the previous version and not installing a new one which leaves the system working but in need of a Java install done manually.

Stupid cross-platform programming and stupid on-the-fly code translation. The people who made Java probably never saw it coming, but Sun and now Oracle are horrible for shoveling Java on the world and developers are all dumb poop heads for compiling junk in Java.

+1 billion... We have had a very difficult time with JAVA... deploy using msi... receive 20+% failure rate due to 2753 errors due to the fact they have no clue how to build an msi installer.

We switched to the exe with 7 update 7, fairly good results...

Then 7 update 11 exe deployment had massive failures due to hanging of the exe process.

Now we found with the release of 13 that a new version/update check has been implemented... not documented mind you. Now users are trying to upgrade when prompted and failing due to rights issues. Found only a marginal way to disable this new prompt (and I suspect disable of check will be disabled itself when a new version comes out).

We cannot deploy every Java version, they come out too frequently, we could probably hire a full time java/adobe middleware packager/deployment person just to keep up to all the updates.
 
Exactly. Except I still use it

Do you use it in the browser? If not, then at least disable it in it's control panel there. Don't trust disabling it in your browser as you'll never know if something or someone will go in and re-enable it. I got hit by that a few months ago via an ad network on popular site. someone was using it to install bit coin miners and botnet clients.
 
Do you use it in the browser? If not, then at least disable it in it's control panel there. Don't trust disabling it in your browser as you'll never know if something or someone will go in and re-enable it. I got hit by that a few months ago via an ad network on popular site. someone was using it to install bit coin miners and botnet clients.

Im actually on this path, we have a lot of resources running of java (not on a browser) that completely throwing away java is not an option. heck we are dumb poopheads as SkribbelKat says :(
 
This is a perfect example of what I've been talking about. Updates are NOT the solution. I'll admit I don't really know much about JAVA, but I'm glad I got rid of it instead of updating it. This whole idea that your not protected unless you have all the latest "updates" in laughable.
 
Now we found with the release of 13 that a new version/update check has been implemented... not documented mind you. Now users are trying to upgrade when prompted and failing due to rights issues. Found only a marginal way to disable this new prompt (and I suspect disable of check will be disabled itself when a new version comes out).

Use ORCA to create a custom transform (.MST file).

I configure the following settings in the Properties section:

Property Value [AUTOUPDATECHECK] {0}
Property Value [IEXPLORER] {1}
Property Value [JAVAUPDATE] {0}
Property Value [JU] {0}
Property Value [MOZILLA] {1}
Property Value [SYSTRAY] {0}
 
Back
Top