[tahoe-lafs-trac-stream] [Tahoe-LAFS] #847: create internal VerifierNode/RepairerNode classes

[Tahoe-LAFS]

#847: create internal VerifierNode/RepairerNode classes
-------------------------+-------------------------------------------------
     Reporter:  warner   |      Owner:  somebody
         Type:  task     |     Status:  new
     Priority:  major    |  Milestone:  soon
    Component:  code     |    Version:  1.5.0
   Resolution:           |   Keywords:  confidentiality integrity verify
Launchpad Bug:           |  repair
-------------------------+-------------------------------------------------

Old description:

> I'd like to have a set of {{{VerifierNode}}} and/or {{{RepairerNode}}}
> classes, created by the nodemaker, which implement {{{IVerifiable}}} and
> {{{IRepairable}}} (but not {{{IFilesystemNode}}}). This would be the
> first step towards fixing #482, by giving us an object that represents
> what we can do with a given verifycap/repaircap.
>
> I'm thinking that these objects might be created with or without the
> integrity information. If without, it would just wrap a storage-index.
> It'd be nice to be able to find out what the SI represents, determine its
> UEB value (by consensus, not by cryptographically-ensured integrity
> values), and then verify/repair the file on the assumption that those
> shares were correct.

New description:

 I'd like to have a set of {{{VerifierNode}}} and/or {{{RepairerNode}}}
 classes, created by the nodemaker, which implement {{{IVerifiable}}} and
 {{{IRepairable}}} (but not {{{IFilesystemNode}}}). This would be the first
 step towards fixing #482, by giving us an object that represents what we
 can do with a given verifycap/repaircap.

 I'm thinking that these objects might be created with or without the
 integrity information. If without, it would just wrap a storage-index.
 It'd be nice to be able to find out what the SI represents, determine its
 UEB value (by consensus, not by cryptographically-ensured integrity
 values), and then verify/repair the file on the assumption that those
 shares were correct.

--

Comment (by daira):

 See https://github.com/tahoe-lafs/tahoe-lafs/pull/408 .

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