[tahoe-lafs-trac-stream] [tahoe-lafs] #1425: blacklist support

[tahoe-lafs]

#1425: blacklist support
-----------------------------------+-------------------------------------
     Reporter:  warner             |      Owner:  davidsarah
         Type:  enhancement        |     Status:  new
     Priority:  major              |  Milestone:  1.9.0
    Component:  code-frontend-web  |    Version:  1.8.2
   Resolution:                     |   Keywords:  blacklist review-needed
Launchpad Bug:                     |
-----------------------------------+-------------------------------------
Changes (by warner):

 * keywords:  blacklist design-review-needed => blacklist review-needed
 * owner:  warner => davidsarah


Comment:

 That new patch adds the following:

      * allow comments, spaces, blank lines in access.blacklist
      * always check, not just when access.blacklist was present at boot
      * log prohibited file access (to twistd.log)
      * report blacklist parsing errors
      * mention need for atomic blacklist updates in docs

 While testing, I noticed that doing the check in {{{NodeMaker}}} means
 that listing a directory will fail if one of the objects inside it is
 prohibited: the directory-listing code creates a Filenode for each object
 (to extract the readcaps/writecaps separately, I think), and that step
 fails. Should we fix that? By doing the check somewhere else (maybe
 Filenode.read?) we could allow directories to mention the prohibited item,
 which might be a usability win.

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