Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firefox has started blocking unsigned extensions #569

Closed
pcause opened this issue Aug 5, 2015 · 13 comments
Closed

Firefox has started blocking unsigned extensions #569

pcause opened this issue Aug 5, 2015 · 13 comments

Comments

@pcause
Copy link

pcause commented Aug 5, 2015

I run from Nightly, and I installed the latest and I just noticed that it is disabled. Firefox says it is disabled because it is unsigned. Mozilla announced intent to do this and apparently they have started to enable. If you use nightly or developer addition you can toggle (make true):

xpinstall.signatures.required

and install the latest from github. Mozilla site says that if you use released or beta this option isn't available.

@Bec-de-Xorbin
Copy link

Why don't you install it from here? https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/

@pcause
Copy link
Author

pcause commented Aug 5, 2015

I usually pull development releases so I've just pulled from github.

@AmrEldib
Copy link

AmrEldib commented Aug 6, 2015

Maybe documentation should be updated to add the xpinstall.signatures.required fix for people who are installing the unsigned release.

@5t3f4n
Copy link

5t3f4n commented Aug 6, 2015

While having self-hosted (i.e. hosted outside of AMO) extensions signed is possible, it still requires review from Mozilla. I think gorhill (when on a roll) releases new builds at a pace that is too fast – sometimes two in a day. Unless the review process is improved.

@AmrEldib

the xpinstall.signatures.required fix

This won't be possible in Firefox Stable or Firefox Beta after the next update.

@wohali
Copy link

wohali commented Aug 11, 2015

I installed 1.0.0.1 from https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/ and it still lists as unsigned. Am I doing something wrong?

@gorhill
Copy link
Owner

gorhill commented Aug 11, 2015

uBlock Origin from AMO is signed, so you should not have any warnings when you install -- all extensions from AMO are signed.

@gorhill
Copy link
Owner

gorhill commented Aug 12, 2015

I created a development channel on uBlock Origin's page on AMO: scroll to the bottom, expand Development Channel.

My understanding is that this AMO-hosted beta build is signed, and it will auto-update whenever I push a new beta version. I installed it on the release version of Firefox 40, and it went fine.

@pcause
Copy link
Author

pcause commented Aug 12, 2015

I just went there and looked and the developer channel in the site says you can't install these versions of uBlock on released versions of Firefox. From what I've read released means released and beta. Not an issue for me as I use nightly, but may be for others.

ublock

@gorhill
Copy link
Owner

gorhill commented Aug 12, 2015

the site says you can't install these versions of uBlock on released versions of Firefox

I know, but somehow I could install it fine on Firefox 40 on my side (Linux).

@kintpuash
Copy link

On the new uBlock development channel installed from AMO on Firefox beta (41). Extension updated earlier today. No warnings in addon-manager, no problems.

@gorhill gorhill closed this as completed Aug 22, 2015
@gwarser
Copy link
Contributor

gwarser commented Nov 1, 2015

ubo
Fx 43 on win7, uBO from AMO dev channel 1.3.3b2
xpinstall.signatures.required;false

ubotrue
xpinstall.signatures.required;true

#565 (comment)

@yupi2
Copy link

yupi2 commented Nov 1, 2015

@gwarser
Doing the following worked perfectly for me on a new firefox (nightly and stable) install & profile:
#569 (comment)
Make sure to backup any settings from an install and remove uBO if it was installed from github.

@magicgoose
Copy link

Unfortunately, regular Firefox doesn't allow turning off this blocking.
Maybe it's time to switch to GNU IceCat…

Repository owner locked and limited conversation to collaborators Aug 30, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants