Dragon NaturallySpeaking Rich Internet Application Support plugin has been Blocked again
Oh, it is Unsigned. Pity about that. Is it ever likely to be submitted for it to be accepted? Not likely. Nuance - that make Dragon, are unlikely to ever want to get approved for anything they do unless it is to Microsoft. That's the kind of people they are. Is there anything wrong with the App? Not likely. Is it an app that is required to be used by people with a Disability who could be located anywhere in the world? Sure, very likely. But apparently that doesn't seem to mean very much to the Admins who have decided to Block the App again. I have set 'xpinstall.signatures.required' to 'false' but even with that set to 'false' Firefox seems to be somehow checking again for a signature and the App is blocked. Why? Why cant we Dragon users be allowed to keep running an App that can make such a difference to our life? What if we have to use the App to carry on our work, should we be forced move away from the Firefox that we love to something else that allows our App to run? i have been an avid Firefox user, supporter and advocate since your first Public beta was released. I do not want to be forced to the other lesser browsers.
Help me understand why this has been blocked and how to get the functionality back again.
تمام جوابات (1)
As of Firefox 48 'xpinstall.signatures.required' is gone; it was a temporary preference to allow add-on developers a lot more time to "get with the program" and get their Firefox extensions verified and signed.
Close to two years ago extension developers of record with Mozilla were notified that a signing / verification scheme would be coming in the future. This blog announced it to the public at large. https://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience/ This is a follow up blog with further details. https://blog.mozilla.org/addons/2015/04/15/the-case-for-extension-signing/
iirc, this signing / verification was originally slated for Firefox 40, and was postponed multiple times and eventually was enforced with Firefox 48. Pushed back like 50 weeks total. If a company like Nuance can't fix their stuff in a year, they oughta hand their heads in shame and just tell their users that they aren't going to support Firefox any longer and do it up front.
My advice is to switch the the ESR version which won't have mandatory signing / verification until Firefox 52 comes out in March of 2017. https://www.mozilla.org/en-US/firefox/organizations/faq/