[or-cvs] r16912: {updater} RE-clarify what parts of the system need admin privileges, s (updater/trunk/specs)

[nickm@xxxxxxxx]

Author: nickm
Date: 2008-09-15 10:32:04 -0400 (Mon, 15 Sep 2008)
New Revision: 16912

Modified:
   updater/trunk/specs/glider-spec.txt
Log:
RE-clarify what parts of the system need admin privileges, since apparently that is not obvious even to smart people.

Modified: updater/trunk/specs/glider-spec.txt
===================================================================
--- updater/trunk/specs/glider-spec.txt	2008-09-15 05:31:59 UTC (rev 16911)
+++ updater/trunk/specs/glider-spec.txt	2008-09-15 14:32:04 UTC (rev 16912)
@@ -120,10 +120,15 @@
           these packages will be platform-dependent: they could be pkg
           files on OSX, MSI files on Win32, RPMs or DEBs on Linux, and
           so on.  Glider should query the user for permission to start
-          installing packages, then install the packages.  (All other
+          installing packages, then install the packages.  All other
           steps should generally happen automatically, in the
-          background, without needing user intervention.)
+          background, without needing user intervention.  This part
+          needs user intervention because (A) it isn't nice to install
+          updates without permission, and (B) in some configurations,
+          it needs administrator privileges.
 
+          (NO OTHER PART of this design needs administrator privileges.)
+
 1.1. The repository
 
    Each Glider instance knows about one or more "repositories".  A
@@ -323,7 +328,7 @@
    used to sign documents.  The type determines the interpretation of
    KEYVAL.
 
-   The ID of a key is the type field concatenated with the SHA-256
+   The ID of a key is a two-element list of the type and the SHA-256
    hash of the canonical encoding of the KEYVAL field.
 
    We define one keytype at present: 'rsa'.  The KEYVAL in this case