![]() ![]() Without going into too many details, here is what is happening: You are probably wondering what the few lines of code do, and whether it is save or dangerous. Once done, you may once again install any add-on, signed or unsigned, in Firefox Stable or Beta just like before. Step 3: Install unsigned add-ons in Firefox Stable or Beta. C:\Program Files\Mozilla Firefox\defaults\pref ![]() Move the file into the defaults\pref folder of the Firefox program folder, e.g.Create a second text document on the desktop and open it afterwards in an editor.Make sure you place the file in the root program folder of Firefox. Please note that you are free to select any installation directory, and that you may run Firefox as a portable program as well. On Mac, it is /Applications/Firefox.app.On Linux, it is /usr/lib/firefox- or /usr/lib64/firefox.On Windows, this is either C:\Program Files\Mozilla Firefox\ or C:\Program Files (x86)\Mozilla Firefox\.Move the config.js file in the Firefox installation folder.Make sure it is called config.js and not config.js.txt. Make sure you copy all of it, including the two // in the first line (See screenshot above).Ĭ("resource://gre/modules/addons/XPIProvider.jsm", ) Paste the following code into the document.Leave the name for the time being, and open the text document afterwards by double-clicking on it.You can do so on Windows by right-clicking on the desktop and selecting New > Text Document. The method requires that you create two new files and place them in the main Firefox installation / run folder. Override the Firefox Add-on Signing enforcement You need to install and use Firefox ESR to disable add-on signing in the Firefox web browser (if you don't want to use Firefox Dev or Nightly builds).Īll that is required in Firefox ESR is to set the preference to False on about:config. Update: The method does not seem to work anymore. These add-ons cannot be installed in Firefox Stable or Beta in that case. Firefox Dev, Nightly and ESR users can install unsigned add-ons however after making a change in the preferences.Īdd-on developers get access to unbranded Firefox builds which are stable versions of Firefox that still support the preference.Īll add-ons submitted to Mozilla's main add-on repository are signed, but that is not necessarily the case for add-ons distributed through other channels.Īdd-ons provided by applications, security software comes to mind, on development platforms like Github, and old add-ons that are not in development anymore, may not be signed. This means that Firefox users who run Stable or Beta versions of the browser can only install signed add-ons in the browser. Mozilla implemented the add-on signing security feature in Firefox some time ago, and made it mandatory in Firefox 48 for the Stable and Beta channel.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |