How can I install modified addon?

[vsub]

There is one addon on which I just want to change the hotkey(changing 1 to 3)in a single file but firefox says that the addons is corrupted which is not true and it says so because of that md5 sha1 singing
xpinstall.signatures.required to false does nothing

If someone know of a better addon,that actually does what I want,that that will be better
https://addons.mozilla.org/en-US/firefo ... o-go-back/

I was using this one until now
https://addons.mozilla.org/en-US/firefo ... -close-we/
but that addons don't work on https sites

My XButton1 on my mouse is sending "go back" and I want to close the tab is there is no history

[Brummelchen]

go developer edition (current 65 beta, beta in general only) or create account here to submit your changes and signed
https://addons.mozilla.org/

ofc it has benefit about the structure of extensions, when submitting an extension you will get the error report

[vsub]

Do you mean installing the beta will allow me to install the modified addon?
If yes,then I just tried FF65 beta and I get the same thing,FF says that the addon is corrupted.

After changing the file in the addon,the MD5 and SHA1 will obviously change and I probably need to add the new MD5 and SHA1 but I don't know how to get them and what to do with the files in META-INF(manifest.mf mozilla.rsa and mozilla.sf)

[RobertJ]

.
Although in the past you could edit add-ons, you cannot edit add-ons any longer.. It is a security thing.

.

[vsub]

Yes,thanks for that FF,I feel so much safer and better after I lost tons of customizations,40+ addons,scripts and styles and so on.
It's like I am starting to use FF all over again from v1.??

Does at least the alpha\nighty builds allow to breathe a little bit easier or it is as restricted as the official release?

[Brummelchen]

nightly is NOT recommended, only developer beta.
the problem for dev-editions and security that you dont have verification for any extension, so also malware can bring you down.

for extensions
https://developer.mozilla.org/en-US/doc ... Extensions

best solution for regular users is to speak up as a comment on the addons page.
the one extension is outdated (2017) and the other one has issues.
so it seems there is more to fix than a key-binding.

[RobertJ]

Does at least the alpha\nighty builds allow to breathe a little bit easier or it is as restricted as the official release?

No. The extensions API is the same as the release version. The dead horse is totally dead within Mozilla. There are some FF forks out there supported by a few developers but I would not recommend them.

.

[therube]

so also malware can bring you down

Like AMO (with its webextensions) is not rife with malware as it is.


@vsub, In general you're fighting a loosing battle, but read the README.md to get an idea as to what may be required.

[Brummelchen]

i never had issues with adware or malware from AMO - reading comments is recommended. extensions with no comments or few users need investigations, eg. unpacking the xpi with 7zip or winrar. and ofc it need experience with extensions to recognize content.i never would install any with crypted scripts.

README.md - i dont recommend such deep changes within the firefox installation folders - i am not sure if it will survive an update no sure if user can manage it to get full access without screwing windows rights that badly that windows will end up in a mess. windows 7 may easy, but since windows 8 no one with the HOME version should undermine windows, only with pro or higher and with a simple change in GPO.