tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

edit 

[Imported from Trac: page OneHundredYearCryptography, version 27]
zooko 2013-10-09 14:54:53 +00:00
parent 586458fe19
commit b7a02b0941
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
OneHundredYearCryptography.md

@ -28,7 +28,7 @@ Discussion on the tahoe-dev list with Zooko, Brian Warner, Jack Lloyd, and Daira
Zooko posted [//pipermail/tahoe-dev/2011-February/006133.html "back of the envelope" performance constraints]. Bottom-line: you get 30 million ARM instructions to implement one complete digital signature verification. Zooko posted [//pipermail/tahoe-dev/2011-February/006133.html "back of the envelope" performance constraints]. Bottom-line: you get 30 million ARM instructions to implement one complete digital signature verification.
Julian Wälde has [*pipermail/tahoe-dev/2011-March/006237.html posted an actual implementation] of hash-based digital signatures. This scheme apparently isn't actually a *stateless* scheme like the ones discussed above, but it does meet [*pipermail/tahoe-dev/2011-July/006554.html meets] Zooko's [//pipermail/tahoe-dev/2011-February/006133.html performance criteria]. Julian Wälde has [*pipermail/tahoe-dev/2011-March/006237.html posted an actual implementation] of hash-based digital signatures. This scheme apparently isn't actually a *stateless* scheme like the ones discussed above, but it does [*pipermail/tahoe-dev/2011-July/006554.html meet] Zooko's [//pipermail/tahoe-dev/2011-February/006133.html performance criteria].
Brian and David-Sarah wrote [a simulator]source:trunk/misc/simulators/hashbasedsig.py or two to explore performance trade-offs in (stateless) hash-based signature parameters. The output of one run with the following parameters is this (note that the signing times include regeneration of per-message signing keys from a small long-term private key): Brian and David-Sarah wrote [a simulator]source:trunk/misc/simulators/hashbasedsig.py or two to explore performance trade-offs in (stateless) hash-based signature parameters. The output of one run with the following parameters is this (note that the signing times include regeneration of per-message signing keys from a small long-term private key):
``` ```