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

link to Samuel Neves's idea of hash-based encryption 

[Imported from Trac: page OneHundredYearCryptography, version 3]
zooko 2010-06-23 00:05:02 +00:00
parent 6048707fa1
commit a8702b6863
1 changed files with 1 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
OneHundredYearCryptography.md

@ -12,6 +12,7 @@ It's worth noting that AES is being retained more for political/name brand reaso
Open questions:
* Should we use AES-128, AES-192, or AES-256? *Zooko says: maybe AES-128 because it wastes fewer CPU cycles and is plenty secure. Indeed, if you worry too much about the related key model (which I don't since we never use related keys in Tahoe-LAFS) then AES-128 is arguably safer than AES-256! *
* What KDF is used to generate the keys/IVs? I think Zooko suggested using XSalsa20, but I haven't seen a concrete proposal. *Zooko says: per [this mailing list thread](http://tahoe-lafs.org/pipermail/tahoe-dev/2010-June/004424.html) HKDF might be a good choice for KDF.*
* Samuel Neves had an alternate proposal for encryption to use the same or similar mechanisms as we use for hashing: [Samuel Neves proposal](http://tahoe-lafs.org/pipermail/tahoe-dev/2010-June/004487.html).
## Hashing