Slashdot Mirror

← Back to Stories (view on slashdot.org)

Firefox Disables Microsoft .NET Addon

Posted by kdawson on from the with-their-consent-of-course dept.

ZosX writes "Around 11:45 PM Friday night, I was prompted by Firefox that it had disabled the addons that Microsoft has been including with .NET — specifically, the .NET Framework Assistant and the Windows Presentation Foundation. The popup announcing this said that the 'following addons have been known to cause stability or security issues with Firefox.' Thanks, Mozilla team, for hitting the kill switch and hopefully this will get Microsoft to release a patch sooner." Here's the Mozilla security blog entry announcing the block, which Mozilla implemented via its blocklisting mechanism.

5 of 448 comments (clear)

  1. Re:Great by setagllib · · Score: 5, Funny

    Microsoft has put billions of dollars into developing the most effective and efficient security vulnerabilities to date. I can only watch in awe and wonder.

    --
    Sam ty sig.
  2. Re:Plugin-checker by phozz+bare · · Score: 4, Funny

    The TFA makes a reference [...]

    You mean The TFA Article.

  3. Re:How about just disabling Microsoft? by siddesu · · Score: 5, Funny

    FYI, it doesn't help at all !!!

    I have Microsoft disabled (I run Gentoo Linux), and my Firefox failed miserably to disable the .Net plug-in. I spent a day clicking on the menus and recompiling updates, and I still don't get the pop-up :(

    On the bright side, my system now runs 1.27% faster compared to yesterday. It feels like 10% faster, really.

  4. Rule 1: Don't talk about the registry by Norsefire · · Score: 5, Funny

    A friend had a problem with a CD burner app (Nero I think?) and asked me to take a look at it (they weren't too tech savvy). So I took a look and Googled the error and found that it was a problem with a registry key that would screw randomly. The fix was to delete it and if the error came back the fix was to change it to a specific value (which would cause nagging warnings but not make the program fail outright, so deleting it first was the better solution). So when I had fixed it I told him offhandedly, not expecting him to understand, that it was a problem with the registry and if it happens again to give me a call. So a week later he calls and says it had the same problem but I didn't need to come round because he had found a registry cleaner, for cheap, only $39.95... I never mention the word "registry" to non-tech people now.

  5. Re:Nuke it with regedit... by Sponge+Bath · · Score: 4, Funny

    Delete key name '{20a82645-c095-46ed-80e3-08825760534b}'

    Be careful. If you accidentally delete key {20a82645-c095-46ed-80e3-08855760534b}, your machine explodes.