[HN Gopher] A script to allow installing unsigned extensions on ...
___________________________________________________________________
A script to allow installing unsigned extensions on Firefox
Author : TheBrokenRail
Score : 35 points
Date : 2022-09-11 18:01 UTC (4 hours ago)
(HTM) web link (gist.github.com)
(TXT) w3m dump (gist.github.com)
| teddyh wrote:
| Tangent: I just discovered that the Wayback Machine browser
| extension actually has had an official release, most recenly five
| months ago, and no longer has to be installed in this way. (There
| was a rather large gap between Apr 18, 2018 and Feb 18, 2022 when
| the only way to have a working Wayback Machine browser extension
| was to install it directly from the source code.)
| elashri wrote:
| * Firefox on linux (ubuntu to be specific)
| TheBrokenRail wrote:
| It _should_ work on any Linux as long as omni.ja is located at
| /usr/lib/firefox.
| pmontra wrote:
| Anything like that for Firefox Android and the extensions that
| Mozilla didn't whitelist? I followed their procedure for Nightly
| with a custom add-on collection but it didn't work.
|
| https://blog.mozilla.org/addons/2020/09/29/expanded-extensio...
| TheBrokenRail wrote:
| Because Android is more locked down than desktop Linux, there
| unfortunately isn't an easy way to modify Firefox in-place.
|
| If it helps, the biggest issue I had with setting up custom
| extensions on Firefox Nightly Android using spaces in the
| collection name.
| pitaj wrote:
| Collection worked for me
| paulryanrogers wrote:
| For some reason I had to try it twice before it worked for me.
| I started from a brand new collection the second time and
| followed Mozilla docs to the letter.
| ky5 wrote:
| This is great. If FF updates and removes the tweak will it
| uninstall the extensions or otherwise mess them up?
| TheBrokenRail wrote:
| The extensions will just be disabled until the script is rerun.
| elektor wrote:
| Is there a repository of these Firefox unsigned extensions?
| TheBrokenRail wrote:
| Most extensions that exist are on Mozilla's Addons site. And
| unsigned extensions aren't commonly distributed because you
| just can't install them on normal Firefox, only Nightly or
| Developer Edition builds.
|
| The main use-case of this is so that Mozilla doesn't have total
| control over what extensions are allowed to be installed.
|
| It can also be used so you can install extensions you built-
| from-source.
| ThrowawayTestr wrote:
| Any possibility of getting this for windows?
| TheBrokenRail wrote:
| It shouldn't be that hard to do manually.
|
| The process is just extracting a ZIP file (omni.ja), editing
| modules/AppConstants.jsm to have MOZ_REQUIRE_SIGNING set to
| false, then put the ZIP file back together.
|
| A quick Google search led me to https://udn.realityripple.com/d
| ocs/Mozilla/About_omni.ja_(fo..., which seems to have
| instructions for working with omni.ja on Windows.
| capableweb wrote:
| Seems you should be able to read through the script and adjust
| accordingly pretty easily:
| https://gist.githubusercontent.com/TheBrokenRail/c43bf0f07f4...
|
| Seems `firefox/omni.ja` is the relevant file to patch. If you
| run a bash terminal, you might be able to run the script by
| just changing the paths.
___________________________________________________________________
(page generated 2022-09-11 23:01 UTC)