[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2425: Malicious storage nodes

[Tahoe-LAFS]

#2425: Malicious storage nodes
-------------------------------+-----------------------
     Reporter:  communitycube  |      Owner:  daira
         Type:  enhancement    |     Status:  new
     Priority:  normal         |  Milestone:  undecided
    Component:  unknown        |    Version:  1.10.0
   Resolution:                 |   Keywords:
Launchpad Bug:                 |
-------------------------------+-----------------------

Old description:

> An important development to keep a network clean from sybil and malicious
> attacs it's a way to blacklist and detect malicious storage nodes
>
> A malicious storage node it's defined like a node that it's saying that
> it's storing data, but it isn't.
>
> Those parts of files that it's reciving, are lost.
>
> To prevent malicious storage nodes, each client will check file integrity
> to be sure files are accessible.
>
> Client keeps a relation of parts uploaded to each node. When a storage
> node where file were alocated there, is not giving the file, or it's
> answering it doesn't have your file or is not online, after few retries
> in different days this node it's marked as malicious.
>
> Each client will have a list of what he detected as a malicious storage
> node.
>
> Those list can be done in the introducer,too. In this way, introducer
> would prevent to notice about a malicious storage node to possible
> clients.

New description:

 An important development to keep a network clean from pseudospoofing
 ("Sybil") and malicious attacks is a way to detect and blacklist
 unreliable or malicious storage nodes

 An unreliable storage node is defined as a node that says it's storing
 data, but it isn't.

 Those parts of files that it's receiving, are lost.

 To prevent use of unreliable storage nodes, each client will check file
 integrity to be sure files are accessible.

 Client keeps a relation of parts uploaded to each node. When a storage
 node where file were allocated there, is not giving the file, or answers
 that it doesn't have your file or is not online, after few retries in
 different days this node is marked as unreliable.

 Each client will have a list of what he detected as an unreliable storage
 node.

 Those list can be done in the introducer, too. In this way, introducer
 would prevent to notice about an unreliable storage node to possible
 clients.

--

Comment (by daira):

 I changed the term "malicious" in the description to "unreliable". The
 distinction between those is a matter of intent, not observable behaviour;
 what we actually care about (and can detect) is the latter.

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