[tahoe-dev] [tahoe-lafs] #78: Cater to rsync as a target Tahoe client.

[tahoe-lafs]

#78: Cater to rsync as a target Tahoe client.
----------------------------------------+-----------------------------------
 Reporter:  nejucomo                    |           Owner:  somebody 
     Type:  enhancement                 |          Status:  new      
 Priority:  minor                       |       Milestone:  undecided
Component:  code                        |         Version:  0.4.0    
 Keywords:  enterprise backup encoding  |   Launchpad_bug:           
----------------------------------------+-----------------------------------

Comment(by warner):

 hm, perhaps a more open-ended file format could have room for features
 like this in the UEB hash. For example, our current immutable UEB hash is
 specified to be a dictionary, in which e.g. the {{{["crypttext_hash"]}}}
 key contains the flat SHA256d hash of the ciphertext. If the share format
 (or post-decode pre-decrypt ciphertext format) could also be expanded, we
 could add a section for {{{["encrypted_rsync_hashes"]}}}, covered by a UEB
 key named {{{["encrypted_rsync_hash_root"]}}}, ignored by older clients,
 but available for more advanced clients to use for .. whatever it is an
 rsync hash would be useful for.

 (btw, of course we've discussed elsewhere the security implications of an
 extensible format and the possible benefits of explicitly *disallowing*
 extensions like this)

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