Changeset 3358


Ignore:
Timestamp:
May 22, 2007, 8:49:10 AM (14 years ago)
Author:
Nicklas Nordborg
Message:

Fixed spelling and some cross references

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/src/docbook/userdoc/project_permission.xml

    r3332 r3358  
    7979              means linking with other items. For example, if you have permission
    8080              to use a protocol you may specify that protocol as the extraction
    81               protocol when creating an extract from a sample. In the case of plugins,
     81              protocol when creating an extract from a sample. In the case of plug-ins,
    8282              you need this permission to be able to execute them.
    8383              </para>
     
    157157     
    158158      <sect2 id="project_permission.permissions.checks">
    159         <title>How access permissions are checked</title>
     159        <title>Getting access to an item</title>
    160160     
    161161        <para>
     
    241241        </orderedlist>
    242242      </sect2>
    243      
     243
     244      <sect2 id="project_permission.permissions.share">
     245        <title>Share an item to other users</title>
     246       
     247        <para>
     248          This is described in <xref linkend="webclient.items.share" />.
     249        </para>
     250       
     251      </sect2>
     252
    244253      <sect2 id="project_permission.permissions.plugins">
    245         <title>Plugin permissions</title>
    246        
    247         <para>
    248           Another aspect of the permission system is that plugins
     254        <title>Plug-in permissions</title>
     255       
     256        <para>
     257          Another aspect of the permission system is that plug-ins
    249258          may also have permissions of their own. The default is that
    250           plugins run with the same permissions as the user that invoked
    251           the plugin has. Sometimes this can be seen as a security risk
    252           if the plugin is not trusted. A malicious plugin can, for example,
     259          plug-ins run with the same permissions as the user that invoked
     260          the plug-in has. Sometimes this can be seen as a security risk
     261          if the plug-in is not trusted. A malicious plug-in can, for example,
    253262          delete the entire database if invoked by the root user.
    254263        </para>
    255264       
    256265        <para>
    257           An administrator can choose to give a plugin only those
    258           permissions that is required to complete it's task. If the plugin
    259           permission system is enabled for a plugin the default is to deny
    260           all actions. Then, the administrator can give the plugin the same
     266          An administrator can choose to give a plug-in only those
     267          permissions that is required to complete it's task. If the plug-in
     268          permission system is enabled for a plug-in the default is to deny
     269          all actions. Then, the administrator can give the plug-in the same
    261270          permissions as listed above. There is one additional twist to
    262           the plugin permission system. A permission can be granted regardless
    263           of if the user that invoked the plugin had the permission or not, or
     271          the plug-in permission system. A permission can be granted regardless
     272          of if the user that invoked the plug-in had the permission or not, or
    264273          a permission can be granted only if the user also has the permission.
    265           The first case makes it possible to develop a plugin that allows
     274          The first case makes it possible to develop a plug-in that allows
    266275          users to do things that they normally don't have permission to do.
    267           The second case is the same as not using the plugin permission system,
     276          The second case is the same as not using the plug-in permission system,
    268277          except that unspecified permissions are always denied when the
    269           plugin permission system is used.
     278          plug-in permission system is used.
    270279        </para>
    271280       
    272281        <note>
    273           Plugin developers can supply information about
     282          Plug-in developers can supply information about
    274283          the wanted permissions making it easy for the administrator to
    275284          just check the permissions and accept them with just a single
Note: See TracChangeset for help on using the changeset viewer.