OpenPKG CVS Repository
http://www.openpkg.org/cvsweb/cvsweb.cgi
____________________________________________________________________________
Server: cvs.openpkg.org Name: Michael Schloh
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-doc Date: 29-Jul-2002 09:08:14
Branch: HEAD Handle: 2002072908081400
Modified files:
openpkg-doc/handbook openpkg.xml
Log:
Added section on triple userid pair and made small corrections.
Summary:
Revision Changes Path
1.50 +32 -8 openpkg-doc/handbook/openpkg.xml
____________________________________________________________________________
Index: openpkg-doc/handbook/openpkg.xml
============================================================
$ cvs diff -u -r1.49 -r1.50 openpkg.xml
--- openpkg-doc/handbook/openpkg.xml 12 Jul 2002 11:54:52 -0000 1.49
+++ openpkg-doc/handbook/openpkg.xml 29 Jul 2002 07:08:14 -0000 1.50
@@ -219,7 +219,7 @@
as the architecture moves into the finer stages of development.
</para>
<para>
- Will OpenPKG succeed where others have failed? Only time will tell,
+ Will OpenPKG succeed where others have not? Only time will tell,
but engineers all over the world will be involved in making this
decision. OpenPKG is Open Source, meaning that its source code is not
just available for use, but can be manipulated according to the
@@ -707,14 +707,38 @@
+-man/-----|-man7/
+-man8/
- </programlisting>
- </example>
- </sect1>
+ </programlisting>
+ </example>
+ </sect1>
- <sect1>
- <title>RPM Maintained</title>
- <itemizedlist>
- <listitem>
+ <sect1>
+ <title>Security through Userids and Groupids</title>
+ <para>
+ OpenPKG is designed with good security in mind, and thus provides
+ three Userid and Groupid pairs. Whereas one pair might often suffice,
+ the three distinct pairs allow for finer granularity of providing
+ access to operating system resources. In a few cases, a software
+ application will actually require such an abstraction of user and
+ group rights. The first new Userid created at bootstrap time will
+ have the same name as the OpenPKG instance. The second new Userid will
+ resemble the first, only with a '-r' name extension meaning restricted.
+ The third new Userid will resemble the first, only with a '-n' name
+ extension meaning non-privileged. For example, if an OpenPKG instance
+ is bootstrapped to the directory called 'cw', then the three associated
+ Userids will be cw, cw-r, and cw-n. The administrator can read the
+ Unix password file to see the new entries.
+ </para>
+ </sect1>
+
+<!-- FIXME: What about groupids, and put where belong in dev Teil the -->
+<!-- l_susr/l_sgrp = root/wheel; l_musr/l_mgrp = cw/cw -->
+<!-- l_rusr/l_rgrp = cw-r/cw-r; l_nusr/l_ngrp = cw-n/cw-n -->
+<!-- replace l_{fs,np}{usr,grp} with l_{s,m,r,n}{usr,grp} ??? -->
+
+ <sect1>
+ <title>RPM Maintained</title>
+ <itemizedlist>
+ <listitem>
<simpara>
$opkg_root/*
</simpara>
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
