KDE System Administration/Kiosk/Keys
This article contains a listing of known keys that can be used with Kiosk and what they do. How to actually use these keys and other capabilities of Kiosk such as URL restrictions, creating assigning profiles, etc. is covered in the Introduction to Kiosk article.
Application Action Restrictions
Konqueror and Desktop
Using D-Bus To Find More Actions
Authorizing .desktop Files
KDE applications can take advantage of many types of resources such as configuration data, caches, plugin registries, etc. These are loaded from both system-wide as well as from per-user locations on disk. It is possible to restrict use of the per-user resources directories, preventing users from adding to or altering existing shared resources.
This is accomplished by creating a section like this in a configuration file, most often kdeglobals so that it applies to all applications:
[KDE Resource Restrictions]
The following resources can be used as keys and controlled in this manner:
|all||n/a||All resources listed in this table|
|autostart||share/autostart||Apps to start on login|
|data_<appname>||share/apps||Application data for the application named <appname>|
|xdgdata-apps||share/applications||Application .desktop files|
|services||share/services||Protocols, plugins, kparts, control panels, etc. registry|
|servicetypes||share/servicetypes||Plugin definitions, referenced in services registry entries|
|wallpaper||share/wallpapers||Desktop wallpaper images|
In kdeglobals in the [KDE Action Restrictions] group:
- defines whether OpenGL screensavers are allowed to be used.
- defines whether screensavers that manipulate an image of the screen (e.g. moving chunks of the screen around) are allowed to be used.
The timeout is the time in seconds that the user must be idle for before the logout process is automatically started. Be careful with this capability as it can lead to data loss if the user has unsaved files open.
Session Capability Restrictions
autologout goes here as