MS Issued a Fix For Its Unwanted FireFox Extension
As we discussed last February, and again a few days ago after the Washington Post noticed, Microsoft installed without permission a hard-to-remove Firefox extension along with a service pack for .NET Framework 3.5. Reader Pigskin-Referee lets us know that, as it turns out, Microsoft issued a fix a month ago; details here.
And of course, since it's negative towards Microsoft, Slashdot dupes it a few dozen times. That's some quality journalism all-around. Oh, and it was an honest mistake in the first place, not some horrible malicious act.
Of course, if you read the Slashdot comments, you knew that Microsoft had already fixed it, since the comments are always about 10 times more on-the-ball than the actual posts. Sadly, I think the majority of visitors to this site never dive into the comments section and are probably fed a large spoon of bullshit every morning with their news.
Comment of the year
Now there is an 'uninstall' button, but if you press it, the app is only uninstalled for the user who clicked the button, not other users on the computer; there's still no ready means of permanently opting out system wide.
And they also indicate with every update of the .NET framework it may get re-installed for all users when Windows Presentation components are updated...
Their fix is even more sly possibly. Now you have the false illusion of being able to remove it....
And this still doesn't 'fix' the whole issue of installing components / editing the contents of a third party app a user installed without that user's permission.
Instead of installing it and letting you uninstall it if you don't want it, how about they don't install it and make it an optional thing you can choose to install?
Sure, they've come out with an uninstall process. But who here thinks that Ma and Pa PC User have a chance in hell of correctly performing the necessary steps? For that matter, who thinks that the common user of a PC will even be aware of the issue in the first place?
Yes FF allows add-ons. Yes, MS has every right to create an add-on for FF. What really worries me is when a company creates an add-on for the product of their primary competitor which threatens the stability and security of their competitor's product. At a minimum this is dirty pool. To me it just looks like MS continuing to wallow in the sewage of unfair competition.
Okay, now tell me how to get rid of the similarly-uninstallable "Java Quick Starter" that nobody seems to be mad about because it's not Microsoft?
Knowing them, it will leave about 50% of the junk that the addon installed. And 100% of the registry keys they used for it.
"You use a browser I don't like, therefore it's okay if someone messes with it without your permission!"
And yes, that IS exactly what you're saying, and yes, saying it DOES prove you beyond all possible doubt to be the craven idiot you so rightly fear yourself to be.
And no, you weren't just trolling to get a rise out of those oh-so-predictable Slashbots. And finally, yes, that IS what you were about to say in your pathetically futile defense.
Wait, what's the big problem? It sounds to me like they decided to give Firefox support for what is basically .NET's equivalent of Java WebStart. It means you're using a Windows platform... which you are if you're bitching about this. They didn't alter the code for firefox, or anything-- they installed an extension.
It sounds to me like years of opensource Stockholm Syndrome has made freetards deathly frightened of platform integration and compatibility. Do you freak out when Java WebStart support is installed, also?
From the team perspective, they probably viewed it as a positive gesture--while they were updating the clickonce support on IE, they figured they would provide it on Firefox as well to give users a wider range of choice as to what their browser is.
From an enterprise perspective, you probably want to use things like ClickOnce on your company Intranet; that way web applications don't have to be cludged together in either archaic standard javascript or wacky inconsistent non-standard "modern" javascript... you can make consistent interfaces for things like electronic timesheets and such. Chances are, they don't want you removing it unless you know what you're doing. Of course, there's also some tin-foil hat linux moron who is going to remove the extension with their user-level permissions because it says "Microsoft" on it, then complain about the lack of .NET web application to support. Or worse... "WHY ISN'T THIS WRITTEN IN HTML 5? IT'S A WORKING DRAFT SORT OF. HOW ABOUT WxPython?!" One might even surmise that it being user-level monkey-able might make it more open to exploitation than it would be in IE.. (GreaseMonkey, anyone?)
The fact of the matter is, it's platform integration. Nothing more. For most users, ClickOnce is simply convenient. It just bridges them to support for secure sandboxed .NET applications that might be convenient if provided. For wingbats on slashdot, it's A GROSS INVASION OF THEIR OMG PRIVACY THAT THEY DEMAND FOR THEIR PIRATED COPY OF WINDOWS XP.
Since most of you are using a supported platform, your web browser is rather connected to the security and integration of the platform. Thus, it is Microsoft's territory, in the same way Firefox gets updated and extended if you are using Ubuntu or OpenSuSE. Of course, Firefox's biggest security hole is probably Firefox itself, but that's unimportant.
The point being is its a goddamn platform integration plugin and you people are probably afraid of your own shadows. The idea that any of you can use hideously insecure linux or mac systems, then turn around and freak out at a sandboxed .NET application starter is just awkward.
While I have my criticisms of Microsoft, I'm hardly a basher. Despite having lots of familiarity with Macs and a tiny bit of familiarity with LINUX, I use Microsoft operating systems exclusively.
Two things are worth mentioning here. One is that practically any palooka can show up and start one of these threads. Someone probably saw the article in the WP (or an article about the article in WP) and started a thread without doing research and finding out that this is actually an old issue, an issue that was already mentioned back in February on this site, and that Microsoft had issued a fix a month ago. Bone-headed posts happen a lot around here. That doesn't make these threads part of a sinister conspiracy against Microsoft.
The other thing worth mentioning is that frankly, this is worth mentioning again. While the disabled uninstall button was obnoxious, to me the greater wrong here was sneaking in an extension to a competitor's browser through an automatic OS update without informing the user.
but could someone please clarify the "difficult to remove" bit? I "removed" it by going into "add-ons" and clicking "disable". Problem solved as far as I'm concerned.....
Simple: disable != remove
What is the significant practical difference between an add-on that doesn't get loaded because it's disabled and an add-on that doesn't get loaded because it's removed?
Somehow I don't believe that you're a longtime MS app developer and this was enough to move you to Linux.
Hail Eris, full of mischief...
E pluribus sanguinem
And you must enable it in order to uninstall it.
That's what bugs me the most.
If some other operation installed malware on your machine then said it would uninstall cleanly if you just TURNED IT ON and ASKED IT, would YOU believe them? Would you enable it just to turn on the uninstall button?
I sure wouldn't. Whether it was (or claimed to be) from Sony, Microsoft, 3FN, or Linus himself. Why the HELL should I enable malware that actually IS from a company that considers Firefox to be a major competing product line and has repeatedly sabotaged it in the past? ...
And you can bet that, even if Microsoft's malware uninstalls itself cleanly, the next generation of black-hat malware will include plugins that MASQUERADE as later versions of this thing...
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way