gzz-commits
[Top][All Lists]
Advanced

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

[Gzz-commits] manuscripts/Sigs article.rst


From: Benja Fallenstein
Subject: [Gzz-commits] manuscripts/Sigs article.rst
Date: Sun, 18 May 2003 13:42:42 -0400

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Benja Fallenstein <address@hidden>      03/05/18 13:42:42

Modified files:
        Sigs           : article.rst 

Log message:
        org

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

Patches:
Index: manuscripts/Sigs/article.rst
diff -u manuscripts/Sigs/article.rst:1.87 manuscripts/Sigs/article.rst:1.88
--- manuscripts/Sigs/article.rst:1.87   Sun May 18 13:40:53 2003
+++ manuscripts/Sigs/article.rst        Sun May 18 13:42:42 2003
@@ -245,23 +245,6 @@
 
   This needs to be reasoned out carefully.
 
-Ordered
--------
-
-- Keep count of number of signatures made
-
-- use bits of count for choosing
-
-- this is basically a k-time signature made feasible
-  for large k
-
-- mustn't lose count! 
-
-- can't copy key or restore from backup!
-
-- any scheme mapping the *action* of signing uniquely to a number between 0 
and `$q$`
-  will work.
-
 Probabilistic limited
 ---------------------
 
@@ -287,6 +270,23 @@
 - however, collisions *only* invalidate one leaf of the key tree, so 
   it *is* possible to 
   revoke only that leaf, not the whole key.
+
+Ordered
+-------
+
+- Keep count of number of signatures made
+
+- use bits of count for choosing
+
+- this is basically a k-time signature made feasible
+  for large k
+
+- mustn't lose count! 
+
+- can't copy key or restore from backup!
+
+- any scheme mapping the *action* of signing uniquely to a number between 0 
and `$q$`
+  will work.
 
 Analysis: Characterizing one-time signature schemes
 ===================================================




reply via email to

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