[tahoe-lafs-trac-stream] [tahoe-lafs] #568: make immutable check/verify/repair and mutable check/verify work given only a verify cap

[tahoe-lafs]

#568: make immutable check/verify/repair and mutable check/verify work given only
a verify cap
-------------------------+-------------------------------------------------
     Reporter:  zooko    |      Owner:  davidsarah
         Type:  defect   |     Status:  assigned
     Priority:  major    |  Milestone:  1.11.0
    Component:  code-    |    Version:  1.2.0
  frontend-web           |   Keywords:  confidentiality verify repair
   Resolution:           |  usability tahoe-check wui anti-censorship
Launchpad Bug:           |  excess-authority
-------------------------+-------------------------------------------------

Comment (by warner):

 FYI, {{{nodemaker.py}}} already knows how to create immutable
 verifier nodes, which have both {{{check()}}} and {{{check_and_repair()}}}
 methods.

 My untested [https://github.com/warner/tahoe-lafs/tree/mutable-
 verifiernode mutable-verifiernode]
 branch adds mutable verifier nodes, with only {{{check()}}} (but not
 {{{check_and_repair()}}} due to #625).

 So what this needs is:

 * WAPI code (probably in web/filenode.py) to implement a
   {{{VerifyNodeHandler}}} class, which renders something sensible,
   and accepts a {{{t=check}}} and/or {{{repair}}} command to be
   delivered to the verifiernode (and renders the results)
 * a clause in web/directory.py {{{make_handler_for()}}} to create
   these {{{VerifyNodeHandler}}}s when the right sort of URI is
   provided

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/568#comment:18>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage