Changes between Version 13 and Version 14 of Documentation


Ignore:
Timestamp:
Nov 24, 2009, 1:59:55 PM (15 years ago)
Author:
Jörg Steffens
Comment:

move paragraphs to seperate page

Legend:

Unmodified
Added
Removed
Modified
  • Documentation

    v13 v14  
    7979
    8080
     81===== Restrict Access to Appications =====
    8182
    82 ===== disable application =====
    83 
    84 sometimes, applications are installed on the system,
    85 but not all users should not be able to start it.
    86 
    87 uninstalling not always possible,
    88 because some users may use it, or it is part of a larger RPM and the other applications from the RPM should stay on the system.
    89 
    90 different approaches:
    91 
    92 
    93 ====== TryExec ======
    94 
    95 check, if the user is allowed, to execute the application:
    96 
    97 {{{
    98 [Desktop Entry]
    99 Comment=Ganttproject
    100 Exec=/opt/ganttproject/ganttproject.sh
    101 TryExec=/opt/ganttproject/ganttproject.sh
    102 }}}
    103 
    104 If the command that is specified by TryExec is not executable by the user,
    105 the Desktop-Entries is not displayed in the Start-Menu.
    106 
    107 
    108 ====== hide application by modifying the .desktop file ======
    109 
    110 show only, if VMware image exists (and is readable):
    111 
    112 vmware-winnt.desktop:
    113 {{{
    114 [Desktop Entry]
    115 Comment=VMware mit Windows NT starten
    116 Exec=/usr/bin/sudo /usr/bin/sc_vmware.sh /local/vmware/vermka/Windows_NT.vmx
    117 Hidden[$e]=$(test -r /local/vmware/vermka/Windows_NT.vmx || echo "true")
    118 }}}
    119 
    120 ====== permissions ======
    121 
    122 Set application permissions to not executable by normal user and desktop files to be not readable.
    123 Define this in a permissions file under {{{/etc/permissions.d/}}}.
    124 Filename must match a installed RPM name.
    125 
    126 Execute
    127 {{{/sbin/conf.d/SuSEconfig.permissions}}}
    128 
    129 which sets permissions accordanly.
    130 After package installation by YaST, SuSEconfig is called
    131 and sets permissions.
    132 Therefore application is still unaccessable after a package update.
    133 
    134 Example:
    135 /etc/permissions.d/k3b:
    136 {{{
    137 /usr/bin/k3b                                    root.media      750
    138 /usr/share/applications/kde4/k3b.desktop        root.media      640
    139 }}}
    140 
    141 
     83[wiki:"kde/Application Access Restrictions"]