[tahoe-dev] [tahoe-lafs] #266: update helper to take advantage of random-access AES encryption
tahoe-lafs
trac at allmydata.org
Wed Apr 15 12:18:31 PDT 2009
#266: update helper to take advantage of random-access AES encryption
-------------------------------+--------------------------------------------
Reporter: warner | Owner: warner
Type: enhancement | Status: new
Priority: minor | Milestone: eventually
Component: code-performance | Version: 0.7.0
Keywords: helper pycryptopp | Launchpad_bug:
-------------------------------+--------------------------------------------
Comment(by warner):
hrm. Tell me about this "iv" argument: is it a string or an integer? I
think I'd rather have pycryptopp be responsible for the pack-int-to-string
and block-alignment issues.. it is more likely to get them right than I
would.
It would also be nice to be able to pass an offset into {{{process()}}},
so you could create one AES object and then seek around with it (rather
than creating a new AES object for every segment), but if that were a
hassle I suppose I could live without it.
What happens if my segment starts on a non-AES-blocksize boundary?
Incidentally, I added [http://allmydata.org/trac/pycryptopp/ticket/18
pycryptopp#18] to request this feature, having forgotten about this #266
ticket.
--
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/266#comment:8>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid
More information about the tahoe-dev
mailing list