Apache OpenOffice (AOO) Bugzilla – Issue 79906
Extension Manager / unopkg: Implement mechanism to prohibit export of shared extensions
Last modified: 2008-03-12 10:54:51 UTC
When a shared extension is installed it is possible for the user to export the extension to a local directory and reinstall it below My Extensions. This is bad because: a) An Extension Provider might not want that to happen (possible licensing problem) b) A user might make his office use outdated extensions (e.g. Templates which a provided company wide could be copied and used. When the company extensions are updated the user would miss the update). This can very easily happen as users tend to speed up things. On a slow network this becomes likely to happen. Probably this should be implemented on a "per Extension" basis, meaning this is a property of an extension and should not be "smart handled" by just interpreting access rights. Note that unopkg should have a switch to display such attributes as well.
>a) An Extension Provider might not want that to happen (possible licensing problem)< Therefore we need more advanced "lincense and activation" feature. The "simple license" mechanism was only the first step. Removing the export feature is no protection at all when it comes to copy extensions illegally. >A user might make his office use outdated extensions (e.g. Templates which a provided company wide could be copied and used. ...< The user can obtain the extension from different sources and install it, no matter if the same extension is already installed as shared extension. I do not see this as defect.
.
close
again