Changes between Version 2 and Version 3 of OneHundredYearCryptography


Ignore:
Timestamp:
2010-06-23T00:05:02Z (14 years ago)
Author:
zooko
Comment:

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

Legend:

Unmodified
Added
Removed
Modified

  • OneHundredYearCryptography

    v2 v3  
    1313  * 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! //
    1414  * 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 [http://tahoe-lafs.org/pipermail/tahoe-dev/2010-June/004424.html this mailing list thread] HKDF might be a good choice for KDF.//
     15  * Samuel Neves had an alternate proposal for encryption to use the same or similar mechanisms as we use for hashing: [http://tahoe-lafs.org/pipermail/tahoe-dev/2010-June/004487.html Samuel Neves proposal].
    1516
    1617== Hashing ==