https://bugs.documentfoundation.org/show_bug.cgi?id=158781
Gabor Kelemen (allotropia) <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|1 |0 Status|NEEDINFO |UNCONFIRMED --- Comment #4 from Gabor Kelemen (allotropia) <[email protected]> --- There was a change recently in the Expert dialog and now the finalized state of settings is now respected there. Therefore the notion from bug #36019 comment 16 that these settings can be enabled/disabled by the user if they want - is now obsolete. So if an admin really wants to harden the installation (and our current customer is into that), can do so and be sure that the user does not disable the settings there. About unopkg: it can work on different contexts, as the --help text says: --shared expert feature: operate on shared installation deployment context; run only when no concurrent Office process(es) are running! --bundled expert feature: operate on bundled extensions. Only works with list, validate, reinstall; It makes sense that the admins should be able to deploy new extensions to all machines, even if this is not desired for end users. The --shared mode is exactly for that. Therefore, the config keys should be respected if this mode is not used, but ignored if it is. This would forbid the end users from installing extensions for good (no more backdoors via turning off keys in Expert config or using CLI), but keep the option open for admins, who would not be locking themselves out from updating their custom extensions. -- You are receiving this mail because: You are the assignee for the bug.
