Firefox Blocks, Unblocks .Net Framework Assistant

HardOCP News

[H] News
Joined
Dec 31, 1969
Messages
0
Mozilla's vice president of engineering posted an update on his blog today saying that the company has removed Microsoft’s .Net Framework Assistant from the blocklist but there is still more testing to be done. Apparently there was a big brouhaha over the weekend when the plug-in was blocked, there was a workaround that didn’t work and finally the plug-in was unblocked while another may have been blocked. If this all sounds unnecessarily confusing, that’s because it is.

We received confirmation from Microsoft this evening that the Framework Assistant add-on is not a mechanism for exploiting the vulnerabilities detailed in the earlier post, so we’ve removed it from the blocklist. As the blocklist update propagates to clients, the add-on should be re-enabled for users who had it previously enabled.
 
Huh, I was wondering about that. I came into work this morning, fired up Firefox, logged into hardforum.com and then was prompted about Firefox needing to block a dotNet workflow agent and needed a restart.
 
From the mozilla security blog:
http://blog.mozilla.com/security/20...ant-blocked-to-disarm-security-vulnerability/
It’s recently surfaced that it has a serious security vulnerability, and Microsoft is recommending that all users disable the add-on.

Because of the difficulties some users have had entirely removing the add-on, and because of the severity of the risk it represents if not disabled, we contacted Microsoft today to indicate that we were looking to disable the extension and plugin for all users via our blocklisting mechanism. Microsoft agreed with the plan, and we put the blocklist entry live immediately. (Some users are already seeing it disabled, less than an hour after we added it!)
I thought that was rather impressive that Mozilla and Microsoft were 1.) working together to protect users and 2.) pushed out the block so quickly. I didn't know such blocklist functionality was built-in.
 
i just clicked cancel when i was prompted....thats an easy enough fix right there.
 
The other plugin would have been the windows Image presentation foundation plugin Ah geeze let me check the actual name to be correct. So Windows Presentation Foundation (WPF) plugin is the other one. Still disabled I think, I really don't care as when this started I opened a session that had been crashing lots and it didn't! I ran it the while weekend and it didn't crash. Now I see .net assistant 1.1 is active again but I haven't gone back to that session. I didn't notice any of my browsing to be adversely affected (although I don't represent the entire browsing landscape)

So if I find this to be unstable again I'll just remove them.
 
So I want to add them back to the blocklist instead of having to go through the crazy manual registry uninstalls needed.

Anyone know how to? Why can only Mozilla set the blocklist, why isn't it user editable?
 
I knew there was a reason why I didn't like Microsoft silently installing add-ons to my third-party software. It's because said add-ons have exploitable security holes. Woops.
 
Back
Top