[tahoe-dev] [tahoe-lafs] #684: let client specify the encryption key

tahoe-lafs trac at allmydata.org
Wed Apr 22 17:57:37 UTC 2009

#684: let client specify the encryption key
 Reporter:  zooko          |           Owner:            
     Type:  enhancement    |          Status:  new       
 Priority:  major          |       Milestone:  eventually
Component:  code-encoding  |         Version:  1.4.1     
 Keywords:                 |   Launchpad_bug:            
 Per [http://allmydata.org/pipermail/tahoe-dev/2009-March/001383.html this
 tahoe-dev discussion], Shawn Willden has submitted a patch to allow the
 client to choose the encryption key for an immutable file upload.  This is
 a very dangerous feature, because Tahoe doesn't use unique IVs under the
 hood, therefore you lose confidentiality if you ever ask Tahoe to use the
 same encryption key twice.

 We could make this less dangerous by using random IVs.

 Anyway, it is unfortunate that we didn't pay attention to Shawn patch
 until now, simply because there wasn't a ticket for it.  So now there is.

 This is one of the requirements to implement #320 (add streaming upload to
 HTTP interface), which is a ticket that I would love to see fixed.

Ticket URL: <http://allmydata.org/trac/tahoe/ticket/684>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid

More information about the tahoe-dev mailing list