230 |
|
|
231 |
Hypothesis: |
Hypothesis: |
232 |
|
|
233 |
|
- GISP has a obvious exploit, if a hostile peer is able to behave like "dumb" |
234 |
|
peer. More specifically, a hostile peer answers to "SEEN" messages in the |
235 |
|
network, but no dot perform requested operations, e.g., do not provide |
236 |
|
a "RESULT" message for a "QUERY" message. This behaviour allows other peers |
237 |
|
to maintain hostile peers in their routing tables while still hostile |
238 |
|
peers are able to cause problems to the network's operation. "SEEN", "RESULT" |
239 |
|
and "QUERY" messages are part of GISP-3.4 specification. Also, |
240 |
|
a hostile peer is able to use this "dumb" behaviour with other GISP-3.4 |
241 |
|
messages. |
242 |
|
|
243 |
- It is expected that (popular) data items can be found with fewer hops in |
- It is expected that (popular) data items can be found with fewer hops in |
244 |
*some cases* in GISP network w.r.t Chord network, since GISP extends Chord's |
*some cases* in GISP network w.r.t Chord network, since GISP extends Chord's |
245 |
routing table to have more information as a cache |
routing table to have more information as a cache |