16 |
.. Affect-PEGs: |
.. Affect-PEGs: |
17 |
|
|
18 |
|
|
19 |
-PEG document for implementing killer program against the GISP P2P software |
This PEG document describes general properties of a killer program against |
20 |
-for research purposes only |
the GISP P2P software. This program is only used for research purposes and |
21 |
-the goal is to improve GISP's resilience against hostile attacks |
the goal is to improve GISP's resilience against hostile attacks. |
22 |
|
|
23 |
|
In this document we mean with "peer" as an entity which is able to do a |
24 |
|
(limited/simplified/modified) number of regular GISP peer's functionalies. |
25 |
|
|
26 |
Research problems |
Research problems |
27 |
================= |
================= |
28 |
|
|
29 |
- Is GISP resilient against (hostile) attacks or not ? |
For determining whether GISP is resilient against hostile attack, |
30 |
- How severe implications attacks may cause ? |
we want the answers to the following questions: |
|
- How well GISP is able to re-organise after a (hostile) attack ? |
|
31 |
|
|
32 |
Simulation methods |
- Is GISP resilient against (hostile) attacks or not ? |
|
================== |
|
33 |
|
|
34 |
- Use GISP's native code as much as possible |
- How severe implications attacks may cause ? |
35 |
|
|
36 |
|
- How well GISP is able to re-organise after a (hostile) attack ? |
37 |
|
|
38 |
Attacks models |
- Does GISP have *obvious* exploits ? |
|
============== |
|
39 |
|
|
40 |
- Peer just wants to make the network work slower |
- If there are exlpoits, how easily they can be used by an |
41 |
|
hostile peer ? |
|
- Extra network packets / random false queries |
|
|
- Drop random packets |
|
|
- Try to drop packets wilfully |
|
42 |
|
|
43 |
- Peer wants to make searches for some particular informations difficult |
Simulation method |
44 |
|
================== |
45 |
|
|
46 |
- Forward incorrectly if a key is identified correctly |
We will perform simulations on a single desktop computer. We intend |
47 |
- Peer doesn't reply/forward at all |
to use GISP's native code as much as possible. We start our |
48 |
|
simulation process by creating simple scenarios in which: |
49 |
|
|
50 |
- Peer wants to make life difficult for some particular peers, |
- A hostile (or faulty) peer(s) doesn't reply to queries (a "dumb" peer)* |
|
slowing down their queries |
|
|
|
|
|
- Reply false information |
|
|
- Peer doesn't reply/forward at all |
|
51 |
|
|
52 |
- Peer wants to make search for particular information by particular peers |
- A hostile (or faulty) peer(s) tries to drop certain packets/queries wilfully* |
|
difficult |
|
53 |
|
|
54 |
- Forward incorrectly if a key and source IP are identified correctly |
- A hostile (or faulty) peer(s) forwards queries to incorrect destination peers |
|
- Peer doesn't reply/forward at all |
|
55 |
|
|
56 |
- Peer wants to spam a particular identifier |
- A hostile (or faulty) peer(s) gives false information during queries |
57 |
|
|
58 |
- Store lot of dummy key-value-pairs with a specific key |
- A hostile (or faulty) peer(s)'s queries/replies include loads of rubbish, e.g., |
59 |
|
wrong XML-scheme, wrong string/text encoding, or doesn't otherwise follow the protocol |
60 |
|
|
61 |
- Peer wants to spam a random identifier |
- A hostile (or faulty) peer(s) performs many queries randomly |
62 |
|
|
63 |
- Store lot of dummy random key-value-pairs |
- A hostile (or faulty) peer(s) performs many queries wilfully with a certain key |
|
|
|
|
- Delete peer/peers randomly/wilfully |
|
64 |
|
|
65 |
- perform queries randomly |
- A hostile (or faulty) peer(s) stores lot of dummy random key-value-pairs |
|
- perform queries wilfully |
|
66 |
|
|
67 |
- Byzantine-like peer/peers ? |
- A hostile (or faulty) peer(s) stores lot of dummy key-value-pairs with a certain key |
68 |
|
|
69 |
- Peer's reply includes loads of rubbish, e.g., wrong XML-scheme, wrong string |
During the simulation process we will use a single hostile/faulty peer |
70 |
encoding, or not following a protocol itself |
or a group of hostile/faulty peers (fraction of all peers). |
|
- something else ? |
|
|
|
|
|
|
|
|
More to come... |
|
71 |
|
|
72 |
|
By using above scenarios, we want to clarify GISP's properties with regard to research |
73 |
|
questions. |
74 |
|
|
75 |
|
*=We start the simulation process with these scenarios. |
76 |
|
|
77 |
Issues |
Issues |
78 |
====== |
====== |
79 |
|
|
80 |
Nothing yet. |
.. Is there any issues ? |
81 |
|
|
82 |
|
None, yet. |
83 |
|
|
84 |
Changes |
Changes |
85 |
======= |
======= |