Changes between Version 3 and Version 19 of Ticket #46


Ignore:
Timestamp:
2013-09-11T03:41:35Z (11 years ago)
Author:
zooko
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #46

    • Property Cc davidsarah added
    • Property Keywords aes combiner design-review-needed added
    • Property Owner changed from dragonxue to from_pycon
    • Property Milestone changed from to 0.7.0

  • Ticket #46 – Description

    v3 v19  
    1919Practically speaking, it appears that at the moment Tahoe does not use the ability to set an IV except for sequential access into the stream, otherwise always using an IV of all zeros (this is fine because the keys are generated randomly or via content hashing, and thus will always differ, except in the case that you are encrypting identically messages in which case you'll get identical ciphertext, which is a desirable property). We'll have to make some modifications there when it comes time to implement XSalsa20+AES decryption, because XSalsa20's IV is merely a diversification parameter, the counter exists elsewhere in the state (it can be modified in Crypto++ by calling SeekToIteration).
    2020
    21 This is part of the Tahoe-LAFS [https://tahoe-lafs.org/trac/tahoe-lafs/wiki/OneHundredYearCryptography One Hundred Year Cryptography] project.
     21This is part of the Tahoe-LAFS [//trac/tahoe-lafs/wiki/OneHundredYearCryptography One Hundred Year Cryptography] project.
     22
     23This is to be used for Tahoe-LAFS ticket https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1164