Closed Bug 629544 Opened 14 years ago Closed 9 years ago

Blocklist moonlight plugin on linux.

Categories

(External Software Affecting Firefox :: Other, defect)

Product:
External Software Affecting Firefox
Component:
Other
Platform:
All
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: jst, Unassigned)

References

Details

Per bug 582130, the moonlight plugin corrupts memory (environment related) that is likely to be used by other plugins (or even Firefox). We need to block this plugin and notify the authors etc. I'm unclear to me exactly which versions are affected, unfortunately.
Blocks: 582130
Prompted by this, I did some digging. http://code.google.com/p/chromium/issues/detail?id=49743#c55 summarizes it, and in particular http://code.google.com/p/chromium/issues/detail?id=49743#c46 has the smoking gun. I think we want to blacklist old versions of icedtea, and leave moonlight alone.
Of course, right after I spam everyone I discover that chromium-browser still crashes with these recent versions of the plugins. Somehow google-chrome as well as a debug build of chrome are fine. Sorry, I retract my previous comments; I'm not sure what's at fault.
(Sorry for the bugspam, trying to get this info on all relevant bugs.) Thanks to some gnarly debugging help from #moonlight, we found that both moonlight and icedtea have a global symbol called plugin_debug, and they stomp on one another. I am not sure what the fix is -- either plugin is fine alone, it's just the pair that is bad.
Given the recent findings, I don't think block listing is the right answer here. But it's not clear what is, so I'm leaving this open for now...
Moving out of Blocklisting then. Please move back with the necessary blocklist info (name, files, versions) if we are ready to blocklist at a later time.
Component: Blocklisting → Other
Product: addons.mozilla.org → Plugins
QA Contact: blocklisting → other
Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/ If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.