Opened at 2009-11-30T23:48:48Z
Last modified at 2017-03-07T18:38:09Z
#847 new task
create internal VerifierNode/RepairerNode classes — at Initial Version
Reported by: | warner | Owned by: | somebody |
---|---|---|---|
Priority: | major | Milestone: | soon |
Component: | code | Version: | 1.5.0 |
Keywords: | confidentiality integrity verify repair | Cc: | |
Launchpad Bug: |
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.