Helix SwarmHelix Swarm
Loading...

index.html

  • //
  • guest/
  • servaas_goossens/
  • decentprotect/
  • index.html #2
  • View
  • Commits
  • Open Download .zip Download (12 KB) 
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
  3. <html xmlns="http://www.w3.org/1999/xhtml">
  4.   <head>
  5.     <title>Perforce Public Depot: Decentralized Protect Daemon</title>
  6.     <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
  7.     <link rel="stylesheet" href="http://public.perforce.com/public/css/pure.css" type="text/css"/>
  8.     <link rel="stylesheet" href="http://public.perforce.com/public/css/depot.css" type="text/css"/>
  9.   </head>
  10.   <body>
  11.     <div id="outer">
  12.       <div id="page-top"><!-- frames the logo and search -->
  13. 	  
  14.         <!-- logo -->
  15.         <div id="logo">
  16.           <a href="http://www.perforce.com"><img src="http://public.perforce.com/public/images/site_logo.gif" alt="Perforce Public Depot" width="219" height="50"/></a>
  17.         </div>
  18.  
  19.         <div id="search"><!-- search section -->
  20.           <form method="get" action="http://www.google.com/search">
  21.             <div><!-- needed so invisible field will validate -->
  22.               <input type="hidden" name="sitesearch" value="public.perforce.com"/>
  23.             </div><!-- silly invisible field div -->
  24.             <ul class="search-box">
  25.                <li class="left"><input type="text" size="40" name="q" value="" class="search-form"/></li>
  26.                <li class="middle"><input type="submit" value="Search" class="search-button"/></li>
  27.                <li class="right" style="color: black;">Powered by Google</li>
  28.  
  29.             </ul>
  30.           </form><!-- top navbar search form -->
  31.         </div><!-- end search section -->
  32.  
  33.       </div>
  34.       <!-- start site content -->
  35.       <div id="main-body">
  36.         <div id="content-outer">
  37.  
  38.           <div id="content">
  39.  
  40.             <!-- Content starts here -->
  41.             <h1>The Perforce Decentralized Protect Daemon</h1>
  42.  
  43.  
  44.  
  45.               <!-- ABOUT THIS PROJECT -->
  46.               <a name="about"></a>
  47.               <h3>About This Project</h3>
  48.               <dl class="project">
  49.                 <dt>Content</dt>
  50.                 <dd>
  51.                 <p>
  52.                 The Decentralized Protect Daemon allows regular Perforce users to manage the permissions
  53.                 for parts of the perforce depot without granting them super user access.
  54.                 Each user can recursively delegate part of his responsibility to other users.
  55.                 The super users don't need to spend much time managing the perforce permissions.
  56.                 </p>
  57.                 </dd>
  58.               </dl>
  59.  
  60.               <!-- QUICKLINKS -->
  61.               <div class="quickLinks">
  62.                 <ul>
  63.                   <li><a href="#about"><br/>About</a></li>
  64.                   <li><a href="#overview"><br/>Overview</a></li>
  65.                   <li><a href="#p4protectfile">p4.protect<br/>file</a></li>
  66.                   <li><a href="#masterprotectfile">master.protect<br/>file</a></li>
  67.                   <li><a href="#downloads"><br/>Downloads</a></li>
  68.                   <li><a href="#site">Project<br/>Background</a></li>
  69.                 </ul>
  70.               </div>
  71.  
  72.               <a name="overview"></a>
  73.               <h3>Overview</h3>
  74.               <dl class="project">
  75.                 <dd><p>
  76.                     The Decentralized Protect Daemon reads the permissions from files which may be submitted anywhere 
  77.                     in the depot. These files are named <code>p4.protect</code>.
  78.                     Each <code>p4.protect</code> file contains the local permissions for that directory and all its 
  79.                     subdirectories. The daemon combines all these files into one list 
  80.                     which it applies using <code>p4&nbsp;protect&nbsp;-i</code>. </p>
  81.                     
  82.                     <p>A <code>p4.protect</code> file may only grant permissions using relative paths. The daemon uses 
  83.                     the location of the <code>p4.protect</code> file to make the relative paths absolute.</p>
  84.  
  85.                     <p>Any user that can edit a <code>p4.protect</code> file, may grant him or herself all permissions 
  86.                     for that subtree (including <code>admin</code>). Therefore, write permissions for the 
  87.                     <code>p4.protect</code> files must be given explicitly. It is not possible to grant super user access 
  88.                     by editing a <code>p4.protect</code> file.</p>
  89.  
  90.                     <p>Permissions set in one p4.protect file, can be overridden by another p4.protect file. This 
  91.                     aspect heavily depends on the way Perforce protections are implemented. See 
  92.                     <a href="http://www.perforce.com/perforce/doc.073/manuals/p4sag/04_protect.html#1047007">this 
  93.                     section in Chapter 4</a> of the Perforce <a href="http://www.perforce.com/perforce/doc.073/manuals/p4sag/index.html">
  94.                     System Administrator's Guide</a> </p>
  95.  
  96.                     <p>There's one special file: the <code>master.protect</code> file. It can be 
  97.                     located anywhere in the depot (the exact location can be set in a configuration variable). Only the <code>master.protect</code> file may 
  98.                     grant superuser privileges and may have absolute paths. 
  99.                     </p>
  100.                 </dd>
  101.               </dl>
  102.               
  103.               
  104.               <a name="p4protectfile"></a>
  105.               <h3>The p4.protect file</h3>
  106.               <dl class="project">
  107.                 <dd><p>A <code>p4.protect</code> file consists of up to three sections. 
  108.                 Each section starts with a section header followed by permission lines, which must be indented. 
  109.                 The section header may not be indented. Comment lines start with a <code>#</code> (possibly indented).</p>
  110.                 
  111.                 <p>Example <code>p4.protect</code> file:</p>
  112.  
  113. <table border="1" cellpadding="3" cellspacing="0">
  114. <caption></caption>
  115. <tr><td colspan="1" rowspan="7"><p><code>
  116.   # Permissions for the Plonkels project
  117.   <br/>default:
  118.   <br/>&nbsp;&nbsp;&nbsp;read&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;user&nbsp;&nbsp;&nbsp; emily&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ...
  119.   <br/>&nbsp;&nbsp;&nbsp;write&nbsp;&nbsp;&nbsp; group&nbsp;&nbsp;&nbsp;devgrp&nbsp;&nbsp;&nbsp;*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ...
  120.   <br/>enforce:
  121.   <br/>&nbsp;&nbsp;&nbsp;write&nbsp;&nbsp;&nbsp; user&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 195.3.24.0/24 -...
  122.   <br/>&nbsp;&nbsp;&nbsp;write&nbsp;&nbsp;&nbsp; user&nbsp;&nbsp;&nbsp; joe&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -intf/...
  123.   <br/>&nbsp;&nbsp;&nbsp;write&nbsp;&nbsp;&nbsp; user&nbsp;&nbsp;&nbsp; lisag&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -...
  124.   <br/>&nbsp;&nbsp;&nbsp;write&nbsp;&nbsp;&nbsp; user&nbsp;&nbsp;&nbsp; lisag&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; doc/...
  125.   <br/>protect:
  126.   <br/>&nbsp;&nbsp;&nbsp;write&nbsp;&nbsp;&nbsp; user&nbsp;&nbsp;&nbsp; jim&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; p4.protect
  127.   </code>
  128. </p></td></tr>
  129. </table>
  130. <p/>
  131.                 <p>The following sections are supported:</p>
  132.                   <ul>
  133.                     <li><strong>default:</strong> Permissions in this section may apply to all files except the 
  134.                        <code>p4.protect</code> files. These permissions
  135.                        <em>may be overridden</em> by <code>p4.protect</code> files submitted in a subdirectory of the 
  136.                        current directory.</li>
  137.                     <li><strong>enforce:</strong> Permissions in this section may apply 
  138.                        to all files except the <code>p4.protect</code> files. These permissions <em>may
  139.                        override</em> the default section of this <code>p4.protect</code> and
  140.                        the default and enforce sections of <code>p4.protect</code> files submitted in a 
  141.                        subdirectory of the current directory.</li>
  142.                     <li><strong>protect:</strong> Permissions in this section may only apply to <code>p4.protect</code> 
  143.                        files, including the file containing this section. These permissions <em>may
  144.                        override</em> the protect sections of <code>p4.protect</code> files 
  145.                        submitted in a subdirectory of the current directory.</li>
  146.                   </ul>
  147.                 <p>The syntax of a permission line is very similar to the Perforce syntax for permission lines.
  148.                 It uses the same five fields: Access Level, User/Group, Name, Host and Files.
  149.                 See <a href="http://www.perforce.com/perforce/doc.073/manuals/p4sag/04_protect.html#1059262">Chapter 4</a>
  150.                 of the Perforce <a href="http://www.perforce.com/perforce/doc.073/manuals/p4sag/index.html">System 
  151.                 Administrator's Guide</a> for more details on these fields</p>
  152.                 <p>For <code>p4.protect</code> files the following restrictions apply:</p>
  153.                 <ul>
  154.                   <li>The Access Level cannot be <code>super</code>.</li>
  155.                   <li>The Files field cannot start with a slash ('<code>/</code>'), i.e. it must be a relative path.</li>
  156.                 </ul>
  157.                 </dd>
  158.               </dl>
  159.  
  160.              <a name="masterprotectfile"></a>
  161.               <h3>The master.protect file</h3>
  162.               <dl class="project">
  163.                 <dd><p>The <code>master.protect</code> file has the same structure as the <code>p4.protect</code>
  164.                 file. It can be seen as the top-level <code>p4.protect</code> file. Its <code>enforce</code> and 
  165.                 <code>protect</code>
  166.                 sections may override the permissions set in all <code>p4.protect</code> files.
  167.                 </p>
  168.                 <p>The restrictions to the Access Level and File fields do not apply to the 
  169.                 <code>master.protect</code> file. Thus, this file is the only place where super users are 
  170.                 defined. All Files fields must contain absolute paths.</p>
  171.                 </dd>
  172.               </dl>
  173.               
  174.               <!-- DOWNLOADS -->
  175.  
  176.               <a name="downloads"></a>
  177.               <h3>Downloads</h3>
  178.               <dl class="Dwnload">
  179.                 <dd>
  180.                   <ul>
  181.                     <li>
  182.                     <em>todo</em></li>
  183.  
  184.                   </ul>
  185.                 </dd>
  186.               </dl>
  187.  
  188.               <!-- PROJECT BACKGROUND -->
  189.               <a name="site"></a>
  190.               <h3>Project Background</h3>
  191.  
  192.               <dl class="pbacksite">
  193.                 <dd>
  194.                   <p>The Decentralized Protect Daemon has been in use since 2003 at <a href="http://www.ortec.com">Ortec</a> in the Netherlands.
  195.                   It is developed and maintained by Servaas Goossens (s goossens at ortec dot n l) 
  196.                   and published under the GNU GPL in february 2008.</p>
  197.                 </dd>
  198.               </dl>
  199.  
  200.               <div class="hr-dotted"></div>
  201.  
  202.               <p class="stored-file">You're browsing a file stored as <code>$Id: //guest/servaas_goossens/decentprotect/index.html#2 $</code>
  203.               </p>
  204.             <!-- Content ends here -->
  205.  
  206.           </div><!-- id content -->
  207.  
  208.         </div><!-- id content-outer -->
  209.  
  210.       </div><!-- id main-body -->
  211.  
  212.  
  213.       <!-- Copyright and bottom bar -->
  214.  
  215.       <div id="copyright">
  216.         <p>The decentprotect script and the above documentation is Copyright &#169; 2008 Servaas Goossens;<br/>
  217.         See the file <a href="COPYING">COPYING</a> for license terms.<br/>
  218.         All the rest is Copyright &#169; 2008 Perforce</p>
  219.       </div>
  220.  
  221.     </div>
  222.   </body>
  223. </html>
# Change User Description Committed
#2 6236 Servaas Goossens Filetype +k for index.html 17 years ago
#1 6235 Servaas Goossens Decentralized Protect Daemon:
* Add index.html file (work in progress!)
* Fix bug in comp...lain_to_submitter
* Improve error reporting (use formatException())
* Make closemailport() more robust in case smtp server has already disconnected. «		 17 years ago