[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]

#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:           |
-------------------------+-------------------------------------------------
Changes (by zooko):

 * milestone:  1.10.0 => eventually


Comment:

 I briefly put this ticket into the 1.10 Milestone, but then I realized we
 don't want to break backwards compatibility with Tahoe-LAFS v1.6, because
 it ships with Ubuntu 10.04 Lucid:

 http://packages.ubuntu.com/search?keywords=tahoe-
 lafs&searchon=names&suite=all&section=all

 Lucid is an Ubuntu "Long Term Stable" release, is supported by the Ubuntu
 project and/or Canonical until 2015, and in all likelihood will be widely
 used at least until then. We should be cautious about making any change
 that breaks backward compatibility with Tahoe-LAFS v1.6.

 Moving this ticket to Milestone "eventually".

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