Changes between Version 24 and Version 25 of Ticket #1164


Ignore:
Timestamp:
2014-12-30T22:04:48Z (7 years ago)
Author:
daira
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1164 – Description

    v24 v25  
    1010And to make it so that caps of that new type get encrypted/decrypted with XSalsa20+AES-128 instead of with AES-256. For the first release of Tahoe-LAFS which includes that functionality, it will still by default create new caps using the old encryption of only AES-256. It is important that people feel free to upgrade to new versions of Tahoe-LAFS without having to take any steps to ensure backward-compatibility, and that means that the new version of Tahoe-LAFS ''must not'', by default, produce caps that older versions of Tahoe-LAFS (such as v1.8.0) can't read.
    1111
    12 [//pipermail/tahoe-dev/2010-August/004936.html This tahoe-dev letter] listed all the places where the source code used encryption. Here are those links updated to current master:
     12[//pipermail/tahoe-dev/2010-August/004936.html This tahoe-dev letter] listed all the places where the source code as of Tahoe-LAFS v1.8.0c1 used encryption. Here are those links updated to current master:
    1313 * [source:src/allmydata/dirnode.py@35f37cc5#L175]
    1414 * [source:src/allmydata/dirnode.py@35f37cc5#L294]