[tahoe-dev] AES-256 is looking worse

[Brian Warner]

Jan-Benedict Glaw wrote:
> 
> In case of fire, maybe it would be feasible to extend the a repair
> with a writecap to do additional re-crypting?

Hm, yeah, that'd be feasible. Doing "cp -r" would probably be more
straightforward, though, maybe with an option to prohibit re-use of
immutable filecaps (full byte-wise copy of everything).

> Another question is: Will a switch be a real switch? Or just allow
> an additional crypto alg?

It would probably come in the form of a new filecap format ("URI:CHK2"?)
which is defined to either contain an algorithm field (URI:CHK2:AES256:
or URI:CHK2:XSALSA20:), or which just always uses the new algorithm. New
uploads would use the new format, but existing files in both formats
would continue to be readable. Maybe we'd provide a switch to let you
intentionally upload files in the old format (if you want your files to
be readable by older clients), but more likely not.

cheers,
 -Brian