I notice today that Firefox is now blocking Avast Security and Web reputation plugin. How can I get this working again in Firefox?
The latest version of Firefox is blocking a lot of extensions AOS is just one of the.
Avast is working with Firefox to resolve the problem.
Well FF 40.0.2 being the latest regular release of firefox and whilst that flags AOS as not signed, it isn’t stopping it on my win7 system (I don’t have it installed on this XP system).
For now it is possible to enable it within the FF add-ons, come FF 41.0 there will be further changes, but they can be over written in the about:config.
Hopefully by that time the AOS add-on will have been signed and approved.
FF 42.0 will see a further tightening on permitted add-ons.
Snip>"For now it is possible to enable it within the FF add-ons, come FF 41.0 there will be further changes, but they can be over written in the about:config".
David, I’m not sure I understand the “about: configuration” part of your post?
How is that overwritten?
It is a manual setting to disable the signing whitelist etc.
If you set it not to require signatures then you shouldn’t see any flagged as not being signed. Currently that is false, but it may well be changed to true, that could stop unsigned add-ons working. Modifying the about:config setting for it may resolve the problem. Assuming Mozilla don’t put a spanner in the works on that manual hack.
http://www.screencast-o-matic.com/screenshots/u/Lh/1440451822418-48625.png
Thanks David that trick gave me back my Add-ons. Let’s hope all the Add-ons either get the required signatures or this hack holds up for a while.
For me the main concern was the LastPass Add-on.
There are other problems with Firefox:
http://www.screencast-o-matic.com/screenshots/u/Lh/1440452139361-40360.png
I can’t get to gmail and many other HTTPS sites.
I have no problems accessing GMail or other HTTPS sites. However, I’m using Firefox 40.0.2 release version, not a beta version of Firefox.
You’re welcome, I’m glad that you found it worked as I couldn’t confirm it as I’m not yet on FF 41.0.x
It is a manual setting to disable the signing whitelist etc.
If you set it not to require signatures then you shouldn’t see any flagged as not being signed. Currently that is false, but it may well be changed to true, that could stop unsigned add-ons working. Modifying the about:config setting for it may resolve the problem. Assuming Mozilla don’t put a spanner in the works on that manual hack.
Thanks David.
You’re welcome.