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.
The TFA makes a reference to Mozilla's new Plugin checker. I just went there with JavaScript disabled and ...
I just enabled JavaScript and...
How fantastic.
Why do quote and blockquote tags render the same? That's stupid.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
my system now runs 1.27% faster compared to yesterday. It feels like 10% faster, really
Ahhh you must have complied using something other than 386! Congrads on useing "make menuconfig"!!!
Now if I could only learn how to get that damn make-kpkg to work right in Debian so the modules get included in the .dep file... What is a .dep file anyhow? is it just some tar file? I really wanna make a complete custom kernel package that I can move to my other system.... sigh
"Documentation" vs "developers, developers, developers!"
The question is; Could a normal user find the setting namespace and change their UA to report .NET without the autoinstall add-on. I didn't think so.