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
LATFDBS - Look At The Date Before Submitting
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?
that the only reason I have Slashdot on my RSS is for the witty comments only? I used to actually read the article but now, I don't even bother looking at the headline.
If it's wrong, I don't want to be right!
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.
Seriously? And why?
Hail Eris, full of mischief...
E pluribus sanguinem
It's Firefox not FireFox, by now it should be clear to everyone including whoever wrote the title.
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?
it should NOT allow unsigned / unblessed extensions to be installed in the first place. signed extensions like the windows driver signing is the appropriate fix here.
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.
This is going to be around on machine for quite some time still.
"Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
firefox, firefox, firefox, ...
If Microsoft wanted to play nice, it would've offered it as a "really cool thing to install in Firefox", not something that the user has no choice but to install unless they want to leave their system vulnerable.
This Anonymous Coward will be removing this extension by wiping Microsoft of his machine and installing Linux. After 25 years of developing commercial applications for Microsoft platforms, I'm done.
I personally am astounded to think that Microsoft would have the nerve to release an application that uninstalls MY firefox addons!
Scott Hanselman put up a nice post today outlining the whole story. He points out why it turned out this way, how to uninstall it and even put up the source code so you can see their evil ways for those who were too lazy to unzip the xpi.
http://www.hanselman.com/blog/HowToRemoveTheNETClickOnceFirefoxExtension.aspx
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?
Firefox is definitely popular if such an extension is made available in a system update!
The moment you decided to install Windows you decided to trust Microsoft. You decided to trust them to do what is good for you, you decided to rely on there judgment.
Past experience should have warned you. Don't complain now.
It's Firefox, not FireFox.
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
Whiny Open-source posers are bitches, and will never be happy so ignore them as they'd rather flame you than do anything.
I will follow your preference for a few days and NOT hold you responsible for the consequences.
Now tell me, do *you* personally trust Microsoft?
This should probably be a slashpoll too.
No, people clicking things they shouldn't and not being behind a firewall is the reason we have botnets.
If your machine is NAT'd or you're behind a specific firewall and you do not use any vulnerable outgoing applications (i.e. you browse with Firefox and don't have Javascript enabled for sites that cannot be trusted) and you use an e-mail client that is secure and do not open random attachments or files sent to you on memory sticks then there is no reason you should get infected no matter how out of date you are on Windows updates.
Even if you're fully uptodate on Windows updates as many people are if they go to a site with some Javascript exploit that isn't patched or they open an e-mail attachment you're still going to end up with botnets.
There are ever less and less people in the world connecting to the internet directly such that vulnerable Windows services needing to be patched are the main attack vector. Most people are NAT'd through a router that prevents direct connection to their machine nowadays. Dodgy e-mail attachments and dodgy websites/downloads are almost certainly the primary attack vector for trojans nowadays.
Very long time Windows user here. WGA was the first final straw for me but I let it slide for several years....but now with this stunt it has really pushed me over the edge. I have already switched my wife over by purchasing her a Mac Mini. I will be following suit in the next week. Really Microsoft, if wanted me to switch so badly all you had to do was ask. Your wish is my command. Thanks for the memories though.
Slashdot is negative to Microsoft...
.crap to load. I suspect because I had used the FX beta (and that was after I used the special removal tool buried in MS TechNet that is best found using Google). I couldn't update Silverlight or install Visual Studio. I've managed to keep my original install of XP running despite having updated the hardware at every level 3+ times in those ~7 years until .crap came along. .crap is the worst MS software install I have ever experienced. It has the feeling of 'we will force you to Vista' written all over it. There are issues with ATI use of .crap in CCC that I still haven't been able to resolve. CCC worked fine here until .crap was updated. ATI couldn't careless about fixing CCC for users on AGP cards and simply reverted to 'not supported' as a 'don't give a stuff' (DGS) solution.
.crap installed was to strip every part of it from the system and then reload each module in order. MS have never provided a single (one package) that manages to deal with .crap as a collective.
.crap to invade your install of Firefox 3, 3.5 and Minefield?" clearly the answer here would have been "bugger off".
.crap into your standards compliant browser and assist Microsoft to break the web with technologies that extend the web services to Microsoft only clients like we did with JScript and every other opportunity we can find to cause the web to be fragmented into the has windows and has nots and potentially open a security hole with source code that can't be reviewed by the Mozilla team that may or may not destabilize your Firefox browser and slow down start up times?
.crap into Firefox was necessary it should have been done in the open and discussed in the development forum at Mozilla. There is absolutely no excuse for this, it is a deliberate act to extend the browser wars to break the web with technologies that are not required and are specific to the Windows platform.
What a load of crap! Slashdot is totally neutral to all things. We posters are cynical on all issues. We are every bit as cynical about Apple and Linux.
Should MS have done this? Totally NOT. I had to bugger about for a week and finally to reinstall Windows to get
Solutions I tried showed that only way to get
If the question was asked "Do you want
In fact the 'question' if it were honestly put would have been...
"Would you like to install MS
With [YES] & [FUCK NO RACK OFF]
Clearly 99.9% of sane people who understand are going to choose the 'rack off' option.
It's an underhanded attempt to break the web. Nothing more and nothing less. That people here are a tad pissed about it... really I think the reaction to this has been too mild.
The best thing for the web is the removal of Microsoft at the front and backends. We already have the pain in the arse drifting standards of IE to deal with. The CSS, JavaScript and XMLRequest differences.
What's needed is a class action by Web Designers to recover the time required to write Conditional Comments from Microsoft. Why should I or my clients pay for Microsoft browser war. And we should have a class action support by Mozilla for the time it takes to remove this from Mozilla products and have that cash given to the Mozilla Foundation.
If putting
The comments in Slashdot, rather than being 'anti-Microsoft' haven't gone anywhere near far enough. Was it discussed in the Mozilla forum? I'll go look today but I seriously doubt it. Surely we would have heard the screaming.
It breaks security, the Firefox distribution model, the universal web and software etiquette.
How do I capitalize Firefox? How do I abbreviate it?
Only the first letter is capitalized (so it's Firefox, not FireFox.) The preferred abbreviation is "Fx" or "fx".
The "fix" as they call it only disables the MS plug-in for the current user who runs it. The install is system wide, so the only approach that really rips it out is the one that has been detailed in various places, hacking the register and than zapping the file from the system.
It's again complete BS, not "we're sorry we didn't ask, let's undo the damage", but "we're sorry you noticed, here's something that makes it look differently".
You can trust these guys even less than a UK MP with an expense account.
Insert
"Locking -- Details of how to remove the add-on have been shown in previous posts. Discussions on whether the merits of Microsoft doing this are outside the remit of this support forum."
.net got access to Flash to say collect stats that might benefit Silverlight. Or just injected features of Silverlight into Flash.
I wonder how Adobe would react if this was done to Acrobat. Or
I'd like to see someone do some hard tests on this, seriously FF seems slow to start with it enabled and stability has been improved since it was removed. I'd like to know if this was just imaginary.
I never got that FF extension - what did I do wrong?? - I feel so left out.... ;(
Moderated troll because:
– "f**king idiots". If you're going to insult, quit half-assing it. We can say "fucking" here. .NET with my web browser. In fact, most people probably don't.
– I install lots of stuff without examining the source code. Does that give them free reign to deliberately fuck stuff up?
– I do not want, and never have wanted, to use
– Learn to capitalise Firefox correctly, dammit.
PS: You're a fucking idiot. (captcha: "classify")