[tahoe-dev] [tahoe-lafs] #947: Add file-with-metadata caps

tahoe-lafs trac at allmydata.org
Mon Feb 15 05:57:39 UTC 2010

#947: Add file-with-metadata caps
 Reporter:  kpreid            |           Owner:  nobody   
     Type:  enhancement       |          Status:  new      
 Priority:  major             |       Milestone:  undecided
Component:  unknown           |         Version:  unknown  
 Keywords:  inodes, metadata  |   Launchpad_bug:           

Comment(by zooko):

 One reason that I am thinking about this is the "security-related extra
 metadata" that I've been ticketing about tonight: highest-known-version-
 number (#955), petrification-marker (#954), LAFS 301 Moved Permanently
 marker (not yet ticketed), etc.. It would be cool if, when I send you a
 URL containing a Tahoe-LAFS cap to a mutable file, I automatically include
 in that URL the highest version number of that file that I have ever seen,
 thus empowering you to reject rollback attacks which present an older file
 to you when you try to read it.

 That one, at least, can't really be implemented in the indirection-node
 way (because if someone is going to rollback the file, they might also
 rollback the indirection-node), but would have to be in the bundled-with-
 the-original-URL way.

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

More information about the tahoe-dev mailing list