gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] manuscripts/storm article.rst


From: Benja Fallenstein
Subject: [Gzz-commits] manuscripts/storm article.rst
Date: Sat, 15 Feb 2003 14:43:08 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Benja Fallenstein <address@hidden>      03/02/15 14:43:08

Modified files:
        storm          : article.rst 

Log message:
        less about digital sigs

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/storm/article.rst.diff?tr1=1.215&tr2=1.216&r1=text&r2=text

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.215 manuscripts/storm/article.rst:1.216
--- manuscripts/storm/article.rst:1.215 Sat Feb 15 14:35:30 2003
+++ manuscripts/storm/article.rst       Sat Feb 15 14:43:08 2003
@@ -860,15 +860,16 @@
 In a multi-user environment, we usually want only one user
 or group to be able to publish official versions a document.
 It is not yet clear how to do this.
-Signing pointer blocks digitally may be sensible, but
-digital signatures require a public key infrastructure
-and a trusted timestamping mechanism, which
-are hardly feasible for a system intended to be used
-for off-line as well as on-line work.
+Signing pointer blocks digitally may be sensible.
 For long-term publishing, one-time signatures have been
 found useful [anderson98erl]_. Currently, the pointer mechanism
 works only in trusted Storm pools, e.g.
 in a workgroup collaborating on a set of documents.
+
+.. digital signatures require a public key infrastructure
+   and a trusted timestamping mechanism, which
+   are hardly feasible for a system intended to be used
+   for off-line as well as on-line work.
 
 The ability to retain multiple 'current' versions of a document
 can be useful, for example when there is no time to consolidate




reply via email to

[Prev in Thread] Current Thread [Next in Thread]