[Gzz-commits] storm/doc/dartboard/pointer_identities--benja i...

[Benja Fallenstein]

CVSROOT:        /cvsroot/storm
Module name:    storm
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/07/09 21:51:14

Modified files:
        doc/dartboard/pointer_identities--benja: idea.rst 

Log message:
        more

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/storm/storm/doc/dartboard/pointer_identities--benja/idea.rst.diff?tr1=1.3&tr2=1.4&r1=text&r2=text

Patches:
Index: storm/doc/dartboard/pointer_identities--benja/idea.rst
diff -u storm/doc/dartboard/pointer_identities--benja/idea.rst:1.3 
storm/doc/dartboard/pointer_identities--benja/idea.rst:1.4
--- storm/doc/dartboard/pointer_identities--benja/idea.rst:1.3  Wed Jul  9 
21:04:39 2003
+++ storm/doc/dartboard/pointer_identities--benja/idea.rst      Wed Jul  9 
21:51:14 2003
@@ -4,7 +4,7 @@
 
 :Author:  Benja Fallenstein <address@hidden>
 :Created: 2003-07-10
-:Changed: $Date: 2003/07/10 01:04:39 $
+:Changed: $Date: 2003/07/10 01:51:14 $
 
 .. contents::
 
@@ -204,4 +204,31 @@
 - Then, given a path like ``foo/bar/baz``, we can
   find out who ``foo`` is, according to the root;
   who ``bar`` is, according to ``foo``; and who
-  ``baz`` is, according to ``foo/bar``.
\ No newline at end of file
+  ``baz`` is, according to ``foo/bar``.
+
+When any of the keys is revoked, the corresponding
+entity can ask its parent identity to sign a new key.
+The root identity will need out-of-bounds means.
+
+Clearly, a parent entity can misrepresent a child
+entity-- ``foo`` assigns a key of its own to ``bar``
+and can further on sign messages in ``bar``'s name.
+
+It isn't the Storm-using Web surfer who needs
+to put trust in the parent entity, then.
+It's the child entity-- because the parent
+entity can misrepresent the child entity.
+In fact, an entity needs to trust *all* its
+ancestor entities.
+
+(Just like your web hosting company can take your
+pages online and replace them by something else;
+it's the web page author who needs to trust the
+hosting company, not the person reading the page.)
+
+In fact, I believe the problem *cannot* be solved
+without having to trust somebody: Because you cannot
+guarantee that your private key will not be exposed,
+you need to give somebody else the right to assign
+you a new key; which means you need to trust them
+not to assign your key to someone else.
\ No newline at end of file