Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

Learn More

If my extensions are force installed and locked via Group Policy, why are they still removable via addons.mozilla.org?

more options

I've been in the habit of installing extensions and locking them via the group policy editor. This works great as the addons auto download, and the remove button is removed from the add-ons setting page in Firefox after the policy is applied. However, I've noticed that if you goto Firefox's addons website and search for an extension that is installed, that site gives you a remove button. If you click the button, the extension does get removed. Neither rebooting nor reapplying the group policy restores the extension even though the extension is still listed in the policy. They only way to reinstall it, is to manually browse for it on the site again and install it. It seems that removing the extension should not be possible given the policy.

I've been in the habit of installing extensions and locking them via the group policy editor. This works great as the addons auto download, and the remove button is removed from the add-ons setting page in Firefox after the policy is applied. However, I've noticed that if you goto Firefox's addons website and search for an extension that is installed, that site gives you a remove button. If you click the button, the extension does get removed. Neither rebooting nor reapplying the group policy restores the extension even though the extension is still listed in the policy. They only way to reinstall it, is to manually browse for it on the site again and install it. It seems that removing the extension should not be possible given the policy.
Captures d’écran jointes

Toutes les réponses (1)

more options

Looks like you found a bug. I've filed a bug report (see bug 1568921) about this issue so that the developers can take a look.

Thanks for the find.