Issue 67041 - Some "system-wide" settings should not be reserved to lockdown mode
Summary: Some "system-wide" settings should not be reserved to lockdown mode
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: 680m173
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 3.x
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2006-07-05 10:26 UTC by ebischoff
Modified: 2017-05-20 11:31 UTC (History)
2 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description ebischoff 2006-07-05 10:26:11 UTC has mechanisms that allow it to share some settings with its 
englobing environment (Windows, KDE, GNOME, ...). Examples are the name of the 
preferred email program, proxy settings, or accessibility settings. This way, 
the user needs not reconfigure in something that she/he already 
configured in his working environment. 
These system-wide settings are described in a specification available at 
Some new settings have recently been added which are enabled only in "lockdown 
mode". Lockdown mode is controlled by --enable-lockdown flag and allows to 
restrain functionality of, for example for computers of public 
Some of these new settings might be of general interest, i.e. not only in 
lockdown mode. Examples might be the name of the user or the preferred web 
client. The new settings are not documented yet in the specification. 
The decision of which settings should be made general and which ones should 
remain reserved to lockdown mode is not obvious. 
- First reason is the special way that handles some settings 
and that might prevent from picking it up in the environment. 
- Second reason is the information available in the environment itself, which 
might or might not be adapted to the needs of 
The following should therefore be done: 
1. establish a list of the settings that should become general and of the ones 
that should remain restrained to lockdown mode 
2. update the online specification accordingly 
3. implement the result in shell/sources/backends for each environment 
(Windows, KDE, GNOME, ...).
Comment 1 nospam4obr 2006-07-05 10:30:56 UTC
Thanks for submitting the issue.
Comment 2 nospam4obr 2007-11-26 12:36:42 UTC
Probably won't make it into 2.4 (last 2.x release).
Comment 3 nospam4obr 2008-07-22 08:14:39 UTC
maintainer changed.
Comment 4 kai.sommerfeld 2009-10-15 10:09:26 UTC
sb: Can you please have a look.
Comment 5 Stephan Bergmann 2009-10-15 12:22:02 UTC
I am currently changing some aspects of how those configuration platform
backends work, see
 I can take care of this issue once that work is done.
Comment 6 Marcus 2017-05-20 11:31:19 UTC
Reset assigne to the default "".