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: Tuomas J. Lukka
Subject: [Gzz-commits] manuscripts/Sigs article.rst
Date: Mon, 19 May 2003 18:03:15 -0400

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Tuomas J. Lukka <address@hidden>        03/05/19 18:03:15

Modified files:
        Sigs           : article.rst 

Log message:
        rm sidetrack

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

Patches:
Index: manuscripts/Sigs/article.rst
diff -u manuscripts/Sigs/article.rst:1.150 manuscripts/Sigs/article.rst:1.151
--- manuscripts/Sigs/article.rst:1.150  Mon May 19 18:02:31 2003
+++ manuscripts/Sigs/article.rst        Mon May 19 18:03:15 2003
@@ -358,23 +358,23 @@
 private keys
 defined in the virtual tree.
 
-It is also possible to use key boosting to form `$k$`-time
-signature schemes for large `$k$`. For example, for `$k=2^20$`:
+..  It is also possible to use key boosting to form `$k$`-time
+    signature schemes for large `$k$`. For example, for `$k=2^20$`:
 
-- key_boosting_real(5, 4, 160)::
+    - key_boosting_real(5, 4, 160)::
 
-    (q=2^20.0, b=160, s=17.08984375 KB, 
-     r=20 B, h=20 B, 
-     t0=3.41e+03 [~17.035ms], 
-     ts=1.70e+04 [~85.175ms], 
-     tv=8.65e+02 [~4.325ms])
+       (q=2^20.0, b=160, s=17.08984375 KB, 
+        r=20 B, h=20 B, 
+        t0=3.41e+03 [~17.035ms], 
+        ts=1.70e+04 [~85.175ms], 
+        tv=8.65e+02 [~4.325ms])
 
-Of course, there is the common technique to create a tree
-of one-time signatures, where each key at the top signs
-a number of keys below it. Using our scheme is only a variant,
-which may be somewhat more convenient sometimes because
-it only requires storing the number of keys already used,
-not a whole tree of private keys.
+    Of course, there is the common technique to create a tree
+    of one-time signatures, where each key at the top signs
+    a number of keys below it. Using our scheme is only a variant,
+    which may be somewhat more convenient sometimes because
+    it only requires storing the number of keys already used,
+    not a whole tree of private keys.
 
 
 Conclusion




reply via email to

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