Slashdot Mirror
Firefox Disables Microsoft .NET Addon
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.
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.
Last night I was browsing through the headlines on Slashdot's front page. At one point I came across the headline "Sneaky Microsoft Add-On Put Firefox Users At Risk" (story here). While I was reading the text underneath that headline, Firefox's prompt (indicating that it had detected the relevant plugin) popped up. It was so startling that I started wondering whether the browser was reading my mind! Weird stuff.
The TFA makes a reference [...]
You mean The TFA Article.
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.
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.
As Mr. Morden said to Londo Mollari when Londo asked why not just destroy the Narn homeworld ... "one thing at a time, Ambassador, one thing at a time".
"Ahh! I see you're in that indeterminate Schrodinger state where - oh, uh
Delete key name '{20a82645-c095-46ed-80e3-08825760534b}'
Be careful. If you accidentally delete key {20a82645-c095-46ed-80e3-08855760534b}, your machine explodes.
> Now if I could only learn how to get that damn make-kpkg to work right in .dep file... What is a .dep file
> Debian so the modules get included in the
> anyhow?
".dep"? Never heard of it. Nothing to do with Debian, certainly.
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
"On the bright side, my system now runs 1.27% faster compared to yesterday."
Which means that time you spent recompiling everything should pay for itself after about 90 more days of straight Firefox usage.
He who lights his taper at mine, receives light without darkening me.
FIX THE STUPID FUCKING MODERATION INTERFACE!
Filter error: Don't use so many caps. It's like YELLING.
Filter error: Don't use so many caps. It's like YELLING.
Filter error: Don't use so many caps. It's like YELLING.
I AM!