[Mozilla Enterprise] Extensions system wide: policy vs. browser/extensions

[Thomas Besser]

Hi all,

since a long time I'm distributing addons system wide with Firefox ESR 
on Windows through copying the unpacked and renamed extension to 
"$InstallDir$/browser/extensions" (following scenario 2 from 
https://mike.kaply.com/2012/02/09/integrating-add-ons-into-firefox/ 
except the changed path). It still working with FF ESR 60.

Trying to do the same with the new policy "Extensions" 
(https://github.com/mozilla/policy-templates/blob/master/README.md).

With an URL it does work. It is not clear to me, how a "path" have to 
look like. "//path/to/xpi" is what? Please give an example. Can it be 
local on the client computer? E.g. 
"c:\$InstallDir$\some-directory\some-addon.xpi"

I saw a difference that over policies the extension is installed by the 
user (he can deactivate _and_ delete it, if not locked). With the other 
way he only can 'deactivate' it.

What is planned for the future? Will the first way stay in parallel to 
the policy? Or will it be 'deprecated'.

Regards
Thomas

-- 
Karlsruher Institut für Technologie (KIT)
archIT [IT-Management der Fakultät Architektur]
Dipl.-Ing. Thomas Besser
Gebäude 11.40, Raum 010 | Fon +49 721 608 46024
http://www.arch.kit.edu/fakultaet/it-management.php

KIT - Die Forschungsuniversität in der Helmholtz-Gemeinschaft

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5205 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.mozilla.org/pipermail/enterprise/attachments/20180925/da6b5ec0/attachment.p7s>