16 |
.. Affect-PEGs: |
.. Affect-PEGs: |
17 |
|
|
18 |
This PEG document briefly describes the attack methods used by a "killer" |
This PEG document briefly describes the attack methods used by a "killer" |
19 |
program against the GISP P2P software. The program is intended to be used |
program. The program is intended to be used to test GISP P2P software's |
20 |
to test GISP's robustness against hostile attacks. |
robustness against hostile attacks. |
21 |
|
|
22 |
In this document we mean with "hostile peer" as an entity which is able to do a |
In this document we mean with "hostile peer" as an entity which is able to do a |
23 |
(limited/simplified/modified) number of regular GISP peer's functionalies |
(limited/simplified/modified) number of regular GISP peer's functionalies |
40 |
================= |
================= |
41 |
|
|
42 |
GISP does not appear to address the attacks against DHT systems |
GISP does not appear to address the attacks against DHT systems |
43 |
described in Ref_1_ and Ref_2_. |
described in ref1_ and ref2_. Using a simulation process as a |
44 |
|
research method we want the answers to the following questions: |
|
For determining whether GISP is resilient against hostile attack, |
|
|
we want the answers to the following questions: |
|
45 |
|
|
46 |
- Does GISP have *obvious* exploits ? |
- Does GISP have *obvious* exploits ? |
47 |
|
|
48 |
- If there are exploits how easily they can be used by an |
- If there are exploits how easily they can be used by an |
49 |
hostile peer ? |
hostile peer ? |
50 |
|
|
51 |
|
- How severe implications attacks may cause to GISP network ? |
52 |
|
|
53 |
- Is GISP resilient against (hostile) attacks or not ? |
- In general, is GISP resilient against (hostile) attacks or not ? |
|
|
|
|
- How severe implications attacks may cause ? |
|
54 |
|
|
55 |
- How well GISP is able to re-organise after a (hostile) attack ? |
- How well GISP is able to re-organise after a (hostile) attack ? |
56 |
|
|
63 |
|
|
64 |
- A hostile peer(s) doesn't reply to queries (a "dumb" peer)* |
- A hostile peer(s) doesn't reply to queries (a "dumb" peer)* |
65 |
|
|
66 |
|
.. Next you should describe the exact scenarios you want to try, |
67 |
|
so start with the dumb peer and specify it exactly. Then run |
68 |
|
the test. |
69 |
|
|
70 |
|
Scenario |
71 |
|
|
72 |
|
|
73 |
- A hostile peer(s) tries to drop certain packets/queries wilfully* |
- A hostile peer(s) tries to drop certain packets/queries wilfully* |
74 |
|
|
75 |
- A hostile peer(s) forwards queries to incorrect destination peers |
- A hostile peer(s) forwards queries to incorrect destination peers |
110 |
codebase. |
codebase. |
111 |
|
|
112 |
|
|
113 |
.. _Ref_1: http://www.cs.rice.edu/Conferences/IPTPS02/173.pdf |
.. _ref1: http://www.cs.rice.edu/Conferences/IPTPS02/173.pdf |
114 |
.. _Ref_2: http://dcslab.snu.ac.kr/~buggy/p2p/paper/security/Pastry%20--%20Security%20for%20structured%20peer-to-peer%20overlay%20networks.pdf |
.. _ref2: http://dcslab.snu.ac.kr/~buggy/p2p/paper/security/Pastry%20--%20Security%20for%20structured%20peer-to-peer%20overlay%20networks.pdf |