[tahoe-dev] [tahoe-lafs] #956: embed security metadata in parent directory

[tahoe-lafs]

#956: embed security metadata in parent directory
--------------------------------------------------------------------+-------
 Reporter:  zooko                                                   |           Owner:           
     Type:  defect                                                  |          Status:  new      
 Priority:  major                                                   |       Milestone:  undecided
Component:  code-dirnodes                                           |         Version:  1.6.0    
 Keywords:  mutable newcaps newurls metadata forward-compatibility  |   Launchpad_bug:           
--------------------------------------------------------------------+-------

Comment(by zooko):

 Replying to [comment:2 davidsarah]:
 >
 > There is going to be a compatibility problem with doing this, since we
 don't (as far as I can see) have anywhere in the directory format to
 encode new fields that will be ignored by old clients. This will also be a
 problem with several other proposed features, including deep-verify caps
 as described in #308, and extensible directories suggested as part of
 #959.

 There is such a place -- the "metadata" associated with each link. That
 metadata can be supplied by the user through the wapi, but the special key
 {{{'tahoe'}}} cannot be written into by the user (any user-supplied keys
 in the {{{'tahoe'}}} key are silently ignored); see
 [source:src/allmydata/dirnode.py?rev=4195#L78 Adder.modify()].

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