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

Julian's implementation meet's Zooko's performance criteria! (now with links) 

[Imported from Trac: page OneHundredYearCryptography, version 18]
zooko 2012-02-11 04:50:28 +00:00
parent 50607f32af
commit c6ede56908
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

@ -31,7 +31,7 @@ David-Sarah has proposed to use hash-based digital signatures.
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 (stateful) hash-based digital signatures! Exciting fact: his implementation meets Zooko's performance criterion!
Julian Wälde has [posted an actual implementation](http://tahoe-lafs.org/pipermail/tahoe-dev/2011-March/006237.html) of (stateful) hash-based digital signatures! Exciting fact: his implementation [*pipermail/tahoe-dev/2011-July/006554.html meets] 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):
```