[tahoe-dev] [tahoe-lafs] #329: dirnodes could cache encrypted/serialized entries for speed

[tahoe-lafs]

#329: dirnodes could cache encrypted/serialized entries for speed
---------------------------+------------------------------------------------
 Reporter:  warner         |           Owner:  kevan    
     Type:  enhancement    |          Status:  new      
 Priority:  minor          |       Milestone:  undecided
Component:  code-dirnodes  |         Version:  0.8.0    
 Keywords:  dirnode        |   Launchpad_bug:           
---------------------------+------------------------------------------------

Comment(by zooko):

 [source:src/allmydata/dirnode.py#L201]

 The reason is that the encryption of the write-cap uses a random IV.
 There isn't an easy way to make that deterministic and still secure right
 now, so we can't rely on it for testing.

 (Hm, for future reference -- i.e. after Tahoe v1.5.0 -- maybe we ''could''
 generate the random IV as the secure hash of the write cap itself.  That
 would be make it deterministic without, as far as I can currently see,
 losing security.)

 As to the base32-encoded directory tree, that looks okay to me.

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