[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1414: tahoe get on DIR2 URIs fails with error message that is too terse

[Tahoe-LAFS]

#1414: tahoe get on DIR2 URIs fails with error message that is too terse
-------------------------------+-----------------------------
     Reporter:  gdt            |      Owner:  daira
         Type:  defect         |     Status:  new
     Priority:  minor          |  Milestone:  eventually
    Component:  code-frontend  |    Version:  1.8.2
   Resolution:                 |   Keywords:  usability error
Launchpad Bug:                 |
-------------------------------+-----------------------------
Changes (by daira):

 * owner:  davidsarah => daira
 * status:  assigned => new
 * milestone:  soon => eventually


Old description:

> When doing 'tahoe get' and giving a directory URI, I get "302 Found"
> instead of the bits.    Changing DIR2 to SSK gets me bits.  There's no
> good reason not to return the directory contents; 'cat .' on at least BSD
> shows the bits in the directory.  While most people don't want to look
> ever, and the rest only want to look once in a while, being able to
> understand directories is key to a deep understanding of how access
> control works.
>
> Further, the writecaps should be decrypted when the directory is fetched
> with a writecap.

New description:

 When doing 'tahoe get' and giving a directory URI, I get "302 Found"
 instead of the bits.    Changing DIR2 to SSK gets me bits.  There's no
 good reason not to return the directory contents; 'cat .' on at least BSD
 shows the bits in the directory.  While most people don't want to look
 ever, and the rest only want to look once in a while, being able to
 understand directories is key to a deep understanding of how access
 control works.

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

--

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1414#comment:7>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage