Closed Bug 952463 Opened 12 years ago Closed 12 years ago

Plugins running authorization questions enter into a loop when plugin.sessionPermissionNow.intervalInMinutes is set to 0

Categories

(Core Graveyard :: Plug-ins, defect)

26 Branch
x86_64
Windows 7
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 886792
mozilla26

People

(Reporter: c3041095, Unassigned)

Details

Hi everybody. Switched to "Ask to Activate" to all the plug-ins in the Plugins Page Set plugin.sessionPermissionNow.intervalInMinutes to 0 in about:config Setting plugins.click_to_play to True of False in about:config make no difference at this stage. For example at the first plugin running request for Adobe Shockwave by the page the question "Allow www.website_name.com to run Adobe Flash?" pops up. After answering "Allow" on the top right, the second pop up windows (new feature in FF 25) is asking you the same question, but giving you the choice of "Allow Now" or "Allow Now and Remember". Once "Allow Now" is pressed it goes back to answering the first question and so on entering an endless iteration. I was trying to force FF to make me allow the plugins for each request occurrences. Now I have to switch back to plugin.sessionPermissionNow.intervalInMinutes to 1 to make it work. The issue, of course, is that you're vulnerable for 60 seconds after you've allowed the plugin once each time. I don't know how FF would react with other plugins, so I assumed the problem would be exactly the same. Anyway FF is asking me two question to obtain a similar result needlessly. If I switch to "Always Allow" or "Never Allow" in the Plugins Page, the whole activation security questions are skipped. It seems to me the entire "Plugins Authorization" procedure has to be rethought. Good luck and great work always!
If you want to choose every time, please use the addon for that purpose.
Group: core-security
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.