News for hackers. Stuff that matters.
Re:What’s Next for Multi-Process Firefox by gcp on Tuesday August 02, 2016 @04:41PM (#12213230)
I believe Mozilla released a plan for the future of these things which it showed what they wanted to do step by step (e.g. plugins first, etc).

Flash and Media Plugins (video decoders, EME/DRM) have already been sandboxed for several releases. There is a content sandbox in the development versions of Firefox. Of course it won't ship before e10s is considered stable, because that's a hard prerequisite for it. The amount of protection also varies by operating system (Windows and Mac OS X are pretty OK, Linux is still pretty crappy) but obviously that is improving week by week.

Re:What’s Next for Multi-Process Firefox by ryuuchin on Tuesday August 02, 2016 @10:31PM (#12215161)
> Flash and Media Plugins (video decoders, EME/DRM) have already been sandboxed for several releases.

Firefox provides its own sandboxing now? Flash used to use a subset of the Chrome sandbox for Flash but that was restricted to the 32-bit version of the browser. As far as I was aware Firefox just ran it in the plugin-container processes for crash protection and nothing else (if protected mode wasn't being used or if you were on 64-bit Firefox). Does Firefox now make use of OS mitigations and integrity levels for sandboxing the plugin process?

Re:What’s Next for Multi-Process Firefox by cpeterso on Wednesday August 03, 2016 @01:14AM (#12215754)
Like you say, Adobe's Flash sandbox (aka "Protected Mode", based on Chrome's sandbox library) only supports 32-bit Windows. Mozilla wrote its own plugin sandbox for 64-bit Windows because we didn't want to Firefox users to lose sandboxing just because they switched from 32-bit to 64-bit. Adobe's and Mozilla's sandboxes don't use all the same mitigations and some Flash content is currently broken in 64-bit Firefox.

Here is the Firefox bug tracking the 64-bit sandbox work:

https://bugzilla.mozilla.org/show_bug.cgi?id=1165891