<html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">On 10/08/15 22:21, Xavier Guillot wrote: </div> <blockquote cite="mid:55C915ED.3070707@laposte.net" type="cite"> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> Hi, I can't answer to this specific question, but as an user with Firefox as default browser on Ubuntu 15.04 Desktop, if those addons are kept, perhaps they need to be signed. Today when I updated to the latest FF Nightly 42.0a1 on the daily ppa, Mozilla activated the obligation to use only officially signed extensions: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://support.mozilla.org/fr/kb/add-on-signing-in-firefox">https://support.mozilla.org/fr/kb/add-on-signing-in-firefox</a> All 3 Ubuntu addons were automatically desactivated. On the nightly version, there is an option in <a class="moz-txt-link-freetext" href="About:config"><a class="moz-txt-link-freetext" href="About:config">About:config</a></a> to restore the old behavior (xpinstall.signatures.required set to false), but on future normal and beta versions of Firefox, it will not be possible anymore normally. Even if the addons are provided directly in the packages and not on Mozilla site, it is still also possible to validate them. Best regards, Xavier </blockquote> Ubufox was signed a few weeks ago and will be shipped with the Firefox 40 update tomorrow. However, it's only been through preliminary review, and future Firefox versions disable side-loaded addons that haven't had a full review. I'm not sure about the status of the other addons (cc'ing dbarth). Regards - Chris </body> </html>