Closed Bug 1291460 Opened 9 years ago Closed 9 years ago

Reenable support for xpinstall.signatures.required

Categories

(Toolkit :: Add-ons Manager, defect)

47 Branch
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: webmaster, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0 Build ID: 20160623154057 Steps to reproduce: As of Firefox 48 xpinstall.signatures.required is ignored. This isn't acceptable. There are addons which still function, but are not signed, as well as development versions which fix specific bugs, or even user modified versions. It's one thing to not allow these to work by default, which is exactly where this preference came in handy. Actual results: Valid addons are rendered non-functional, and xpinstall.signatures.required being set to false does not correct this. Expected results: Valid addons are rendered non-functional, and xpinstall.signatures.required being set to false overrides this behavior allowing them to function again. I understand the security reasons for this, but this is taking away user choice, and is in short, a regression.
Component: Untriaged → Add-ons Manager
Product: Firefox → Toolkit
(In reply to Loic from comment #1) > https://wiki.mozilla.org/Addons/Extension_Signing That's tantamount to telling me to go use another product. That's hardly a solution when the option existed already and was removed. I don't want to use an unstable nightly, nor an unbranded version, nor do I want to use a development version. I would like the functionality which existed in Version 47 to exist in Version 48. Loss of functionality is a regression. I have no problem with the default setting being whatever Mozilla feels is best, but I still want the option to change that setting to what works for me.
It was always the plan to remove the option from release builds and we haven't heard any reasons to go back on that so far. The unbranded builds are essentially identical to regular releases other than artwork, those should be your choice assuming you want to stay with Firefox and won't switch to development builds.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.