rule_count=

rule_1=,,,,,,,

...

rule_N=,,,,,,,

In the first part of Example 5 6 you can see how to disable browsing with KDE's 

file dialogs outside the $HOME directory by using the list action. The first rule 

disables browsing any directories on the local file system, while the second 

enables browsing in the $HOME directory, which is exactly what we want. You 

can also see that KDE expands the environment variable $HOME. Usually one 

has to put [$e] after the entry name, or even [$ei] to prevent the application 

replacing the entry with the actual environment value's value after saving, but 

this is not necessary everywhere. The second part of Example 5 6 shows how to 

allow the user to open files in the $HOME and $TMP directories but nowhere 

else on the file system (opening files from the Internet is still possible though).

Example 5 6   URL restriction examples

[KDE URL Restrictions][$i]

rule_count=2

rule_1=list,,,,file,,,false

rule_2=list,,,,file,,$HOME,true

[KDE URL Restrictions][$i]

rule_count=3

rule_1=open,,,,file,,,false

rule_2=open,,,,file,,$HOME,true

rule_3=open,,,,file,,$TMP,true

You can also use shell commands in KDE configuration files, as in Example 5 7, 

but do not overuse this feature.

Example 5 7   Using shell commands in KDE configuration files

Host[$e]=$(hostname)

...

[Icons]

Theme[$e]=$(source /usr/share/config/kdeglobals.defaults && echo $Theme)

5.1.6  Resource restrictions

The last lockdown capability we will discuss is KDE resource restrictions, which 

make it impossible for users to override file lookup outside $KDEHOME/share 

(where most KDE applications put their resources like HTML documentation, 

sound files, etc.) with resources lying in $KDEHOME/share. In the first part of 

102 

Linux Client Migration Cookbook   A Practical Planning and Implementation Guide for Migrating to Desktop