[tahoe-lafs-trac-stream] [tahoe-lafs] #925: Information leak to holders of a directory read cap, about whether each dir entry is writeable and the length of its write cap

tahoe-lafs trac at tahoe-lafs.org
Fri Aug 12 21:14:28 PDT 2011


#925: Information leak to holders of a directory read cap, about whether each dir
entry is writeable and the length of its write cap
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:
  davidsarah             |     Status:  new
         Type:  defect   |  Milestone:  eventually
     Priority:  minor    |    Version:  1.5.0
    Component:  code-    |   Keywords:  backward-compatibility privacy
  dirnodes               |  security
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by zooko):

 Replying to [comment:10 davidsarah]:
 > The forward compatibility fix was in Tahoe v1.6.0. Only versions
 *before* that would be broken.

 Oh, good! I remember you and I caring a lot about forward-compatibility
 back then, and now I'm glad we did. :-)

 I'm happy to drop backward-compatibility with Tahoe-LAFS ''older'' than
 v1.6.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/925#comment:11>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage


More information about the tahoe-lafs-trac-stream mailing list