Oracle Settles FTC Charges Regarding Deceptive Java Security Updates (ftc.gov)
An anonymous reader writes: The FTC and Oracle have come to an agreement regarding Oracle's deceptive Java security updates, which only removed recent versions of vulnerable Java SE, but left behind older, insecure versions. Oracle got away without a fine, but will have to overhaul its Java update process to remove older versions as well.
Oracle probably threatened them with a license audit and they'd need to pay eleventy eleven trillion dollars.
Lost at C:>. Found at C.
I noticed this a few months ago when I built a system and had it scanned for compliance and was getting hit with a several year old hole in Java. I was confused because I knew I upgraded Java on the system. Then I realized that the old version was still there. Truth be said, if I build a machine and I don't absolutely need Java on it, it doesn't get loaded. Same goes for Flash.
Select from tblFriends where interesting >= 4;
infinite patience no longer included? truth+mercy=justice for everybody?
Java is going to nag me to update even more!
Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
This seems senseless. What's in it for Oracle to leave ancient versions of Java lying around? Was it just they couldn't be bothered to remove them?
Are there technical obstacles to removing them? And if so, why not tell the user to remove them manually? It's just another line of boiler plate that no one will read or pay attention to, but then it's the user's problem, not Oracle's. Isn't that what TOS are for? To make everything the user's problem?
New versions of Java introduce breaking changes and often aren't compatible with older software. The best solution? Install the versions of Java required by your software and disable Java in the browser. Thanks to NPAPI deprecation, this is practically done for you.
Why is Oracle's software always covered in pukey beige? Oracle's user-interface design looks like you taught IBM Watson how to search the internet for bad UIs and it got so sick and dumped diarrhea all over their software.
Oracle already intentionally supports the concept of multiple versions by allowing Static installations; when an installation is flagged as Static, it is installed separately, using the full build version number as the folder name rather than the major version only (i.e. jre_1.7.25 rather than jre7), Doing this allows you to call multiple different versions of Java independently, based on your needs. However, if I just run the installer as-is, it does an in-place swap of the version; if I go from a standard install of Java 1.7.25 (installed to a folder called jre7) to a standard install of 1.7.55, it just empties the jre7 folder and installs Patch 55 in the same place. The existing installer already removes non-Static versions now, so if they're going to start forcing more removals of older versions, I can only assume that means it will remove even Static installations. This Static removal policy needs to be a command-line toggle that I can prevent. My company utilizes Java as a cross-platform development engine to run one of our major products on. Each version of our software is tied to a specific version of Java, and as such, engineers end up having multiple versions of Java installed to support each version of our software. Because of this, we're always installing newer versions of Java while not wanting to remove the older versions.
They should quit trying to get Ask installed - yep. But also let's get some freakin clarity to the fact that all these updates do most times is break stuff. If there's an update, the browsers now go ape shit until you update. And it can reset your previous settings. Oh and all those old and never to be updated devices out there we need to connect to, now cannot because of the dang Java update to a later level. Brilliant. Every update is now an "OMG CRITICAL SECURITY PATCH! OMG!" It's pretty pathetic.
The FTC's job is to protect the consumer, not be on the corporate kickback payroll.
FTC fines are a perverse incentive that creates predictable costs to the profitable bottom line of the bottom feeders in a corporate plutocracy.
Its like Oracle's performance in the America Cup: unethical, admonished, but ultimately victorious.
Aren't installations that aren't the primary one rather harmless? If the browser doesn't link to them and they aren't on your run path, then they are just harmless bits, no? If anything with evil intent on your system had the power to execute them, then it was already game over.
this looks more like a mistake than anything else. It's nice to see the FTC calling them on it (nobody else had) but punishing companies for a mistake before giving them the chance to correct it wouldn't exactly be fair.
Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
"first, we need to determine precisely what the company is spending on these sailing days..."
if this is supposed to be a new economy, how come they still want my old fashioned money?
bunch'a'losers
if this is supposed to be a new economy, how come they still want my old fashioned money?