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

add performance criterion and point out that Julian's implementation meets it 

[Imported from Trac: page OneHundredYearCryptography, version 16]
zooko 2011-12-21 19:49:19 +00:00
parent d4366c18ed
commit 47035ce2a5
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
OneHundredYearCryptography.md

@ -29,7 +29,9 @@ David-Sarah has proposed to use hash-based digital signatures.
* <http://tahoe-lafs.org/pipermail/tahoe-dev/2010-June/004509.html>
* <http://tahoe-lafs.org/pipermail/tahoe-dev/2010-July/004587.html>
Julian Wälde has posted an actual implementation of hash-based digital signatures! <http://tahoe-lafs.org/pipermail/tahoe-dev/2011-March/006237.html>
Zooko posted ["back of the envelope" performance constraints](https://tahoe-lafs.org/pipermail/tahoe-dev/2011-February/006133.html). Bottom-line: you get 30 million ARM instructions to implement one complete digital signature verification.
Julian Wälde has [posted an actual implementation](http://tahoe-lafs.org/pipermail/tahoe-dev/2011-March/006237.html) of hash-based digital signatures! Exciting fact: his implementation meets Zooko's performance criterion!
Brian and David-Sarah wrote [a simulator]source:trunk/misc/simulators/hashbasedsig.py or two to explore performance trade-offs in hash-based signature parameters. The output of one run with the following parameters is this:
```