[tahoe-lafs-trac-stream] [tahoe-lafs] #1414: tahoe get on DIR2 URis fails

[tahoe-lafs]

#1414: tahoe get on DIR2 URis fails
-----------------------------------+-----------------------
     Reporter:  gdt                |      Owner:
         Type:  defect             |     Status:  new
     Priority:  minor              |  Milestone:  undecided
    Component:  code-frontend-cli  |    Version:  1.8.2
   Resolution:                     |   Keywords:  usability
Launchpad Bug:                     |
-----------------------------------+-----------------------

Comment (by davidsarah):

 I don't think that BSD {{{cat}}} showing the bits is a good argument for
 {{{tahoe get}}} (or the corresponding web-API request) to do so.
 Conceptually, the SSK URI refers to the bits, and the DIR2 URI refers to
 the directory interpretation. In Unix the same pathname is used to refer
 to both. So it makes sense that in Tahoe, a command that fetches file
 contents would succeed for the SSK URI and fail for the DIR2 URI.

 Since you ''can'' see the bits by using the SSK URI, there's no loss of
 functionality in the current behaviour. So I'm inclined to "wontfix" this.

 > Further, the writecaps should be decrypted when the directory is fetched
 with a writecap.

 I completely disagree; that would be effectively creating a new directory
 format that is not the stored format, which seems overcomplicated and
 unlikely to lead to better understanding.

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