Most recent edit on 2007-09-27 22:16:43 by EnigMa [little change]
Additions:
To prevent this, freenet needs a big legal main use. Freenet integration to operating systems may create this legal main use.
Deletions:
To prevent this, freenet needs a legal main use. Freenet integration to operating systems may create this legal main use.
Edited on 2007-09-27 22:15:19 by EnigMa [Big legal main usage to protect freenet from harvest]
Additions:
An attacker can then simply keep a list of all the node references he has seen in response to requests - either requests originated by him or requests which he has relayed. He can map out the entire network simply by running a node.
To prevent this, freenet needs a legal main use. Freenet integration to operating systems may create this legal main use.
Deletions:
An attacker can then simply keep a list of all the node references he has seen in response to requests - either requests originated by him or requests which he has relayed. He can map out the entire network simply by running a node.
Edited on 2007-07-21 14:09:20 by TehAmI [tiny edit: made header h3 like other pages (shouldn't they be h2?)]
Additions:
Node harvesting
Deletions:
Node harvesting
Oldest known version of this page was edited on 2006-04-27 13:22:18 by MatthewToseland []
Page view:
Node harvesting
In the simplest possible terms: If you connect a node to an
OpenNet, you will have a few initial nodes in the
SeedNodes file. These are not enough for good performance; your node will automatically find more nodes from the nodes you already have. The problem is, an attacker can also put a node on the network, and identify nodes in the same way. Once he has found all the nodes on that particular Freenet network, he can attack them or block them, for example on the
national firewall.
DarkNet is immune to harvesting because all connections are fixed, between hopefully trusted peers, added manually via invitations.
All nodes on 0.5 are opennet. 0.7 will support both
OpenNet and
DarkNet. Right now it only supports
DarkNet.
In more detail: Every time your node does a successful request on
OpenNet, the node which is the source of the data will include its own node reference on the Store
Data message. This may be reset by other nodes along the chain, with a low probability. Your node will then, if it needs more nodes, or at random, connect to that node. This process establishes and constructs a
small-world topology for the network.
An attacker can then simply keep a list of all the node references he has seen in response to requests - either requests originated by him or requests which he has relayed. He can map out the entire network simply by running a node.
I2P is even more vulnerable to harvesting than Freenet
OpenNet.