Slashdot Mirror


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.

11 of 266 comments (clear)

  1. So the WaPo reports a story a month obsolete? by Blakey+Rat · · Score: 5, Insightful

    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.

    1. Re:So the WaPo reports a story a month obsolete? by Foofoobar · · Score: 5, Insightful

      When a company like Microsoft 9 out of 10 times makes hostile gestures towards the open source community, are we supposed to run towards them with flowers and candy every time they screw up now and say 'we forgive you darling. lets go have buttsex on the veranda!'?

      I dunno about you but I get screwed in the ass enough and I'm duct taping my shorts and sitting on the porch with a shotgun.

      --
      This is my sig. There are many like it but this one is mine.
    2. Re:So the WaPo reports a story a month obsolete? by gmack · · Score: 5, Insightful

      It is not actually fixed. Even had it been removable in the first place it still would have been bad because they should not have installed it without permission.

    3. Re:So the WaPo reports a story a month obsolete? by ibookdb · · Score: 5, Insightful

      Has firefox fixed the bug where nobody can install extensions that are enabled by default without user intervention?

    4. Re:So the WaPo reports a story a month obsolete? by docbrody · · Score: 5, Insightful

      Oh, and it was an honest mistake in the first place, not some horrible malicious act.

      Not really buying it. It may not have been some horrible malicious act... but it sure was not some 'innocent mistake.'

      Sure, innocent mistakes happen at big companies (like the whole thing with Amazon de-ranking Gay and Lesbian books). But for a company that is a constant target of anti-trust suits, who is notorious for this kind of thing, you think by now that they would be more careful. Its hard to believe that someone internal at Micrsoft didn't realize what was this was doing and just say 'fuck it' - even if it was a low level developer, somebody had to know - at the very least the guy(s) who wrote the code. I mean come on, this took some work to do. Its not like the amazon issue where practically one click of a check box reclassified a whole genre of books... some one had to put finger to keyboard and code this out.

      So I think its really really hard to call this an innocent mistake. Maybe not a 'horrible malicious act' but once again they are injecting their shit into other peoples shit.

    5. Re:So the WaPo reports a story a month obsolete? by melstav · · Score: 5, Informative

      Since you dragged the other discussion into this, allow me to point out a comment in that very discussion which points out why it's nowhere near the same thing. (Like the fact that Sun announced months in advance that they were going to do it, and the fact that you can, in fact remove it.)

      That comment is +5 insightful. You don't even have to drill down to find it. Just scroll a bit. Given that (some of) the comments are regularly more fair and balanced than the article summaries, you ought to at least skim the discussion before you decide whether this guy is bringing something useful to the discussion or just throwing more FUD onto the pile.

  2. Yeah, a fix by mysidia · · Score: 5, Insightful

    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.

  3. Now how about Java Quick Starter? by Anonymous Coward · · Score: 5, Insightful

    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?

  4. Microsoft.. by Anonymous Coward · · Score: 5, Insightful

    Knowing them, it will leave about 50% of the junk that the addon installed. And 100% of the registry keys they used for it.

  5. And the rest of the story... by Anonymous Coward · · Score: 5, Informative

    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

  6. Spaz down, Sparky by Benfea · · Score: 5, Insightful

    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.