Closed Bug 1125891 Opened 11 years ago Closed 11 years ago

Enable the no-admin sandbox for Flash

Categories

(Core Graveyard :: Plug-ins, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

(firefox36 disabled, firefox37 fixed, firefox38 fixed)

RESOLVED WONTFIX
mozilla38
Tracking Status
firefox36 --- disabled
firefox37 --- fixed
firefox38 --- fixed

People

(Reporter: benjamin, Assigned: benjamin)

References

Details

Attachments

(1 file)

Bug 1123245 landed code to support a no-admin-rights sandbox around plugins, but didn't change any prefs to turn it on by default. We want to enable this by default for Flash.
Attached patch bug1125891.patchSplinter Review
Attachment #8554639 - Flags: review?(bobowen.code)
Attachment #8554639 - Flags: review?(bobowen.code) → review+
Comment on attachment 8554639 [details] [diff] [review] bug1125891.patch Approval Request Comment [Feature/regressing bug #]: Mitigation when disabling Flash protected mode, bug 1119941 [User impact if declined]: This mitigates Flash security exploits [Describe test coverage new/current, TreeHerder]: Manual testing is done, but we need nightly/aurora testers to bang on this quickly so that we can consider landing this into beta on Thursday [Risks and why]: This could possibly break some Flash functionality. We don't think that is likely, but there are many unknowns. [String/UUID change made/needed]: None
Attachment #8554639 - Flags: approval-mozilla-aurora?
Comment on attachment 8554639 [details] [diff] [review] bug1125891.patch As this hasn't yet baked with any audience, we don't have a lot of data on the expected fallout. However, from speaking with bsmedberg on irc "My understanding is that Flash should continue to work, and the risk is mainly with unusual Flash APIs or features, not normal web browsing." This category of issue is most likely going to be found with more eyes on the problem. We also have the ability to push a subsequent update to disable the feature if it breaks Firefox w/ Flash usage in some very bad way. Let's push this to Aurora to test and monitor closely for breakage. Aurora+ cc User Advocacy to monitor for feedback.
Flags: needinfo?(tdowner)
Flags: needinfo?(rrayborn)
Flags: needinfo?(cww)
Attachment #8554639 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Marking 36-38 as affected as we don't know exactly where we're going to take this change yet.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla38
Just a FYI, with the Flash blocking going on right now, we're not going to be able to discern anything about issues with Flash in Input.
Depends on: 1126570
Any focused manual testing needed for this? If yes, what should the testing efforts be focused on (e.g. testing of any specific flash sites, testing on specific OS, testing with enabled/disabled Flash Protected mode...)?
The risk here is unknown; we have at least one bug already filed, bug 1126570. We should definitely follow up on cases like that, as well as any other known Flash sites that have caused problems in the past. Otherwise, the primary QA we need here is to carefully watch and triage incoming Flash-related bugs and escalate them quickly.
Comment on attachment 8554639 [details] [diff] [review] bug1125891.patch We've decided to deploy this along with bug 1119941 in beta5.
Attachment #8554639 - Flags: approval-mozilla-beta+
Attachment #8554639 - Flags: approval-mozilla-beta+ → approval-mozilla-beta?
Attachment #8554639 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Disabled for 36b9.
To close the bugzilla loops, we disabled this on all channels in bug 1120993.
Flags: needinfo?(tdowner)
Flags: needinfo?(rrayborn)
Flags: needinfo?(cww)
Resolution: FIXED → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: