Security » History » Version 4
Greg Burri, 11/09/2009 01:34 PM
| 1 | 1 | Greg Burri | h1. Security |
|---|---|---|---|
| 2 | |||
| 3 | 3 | Greg Burri | This page lists some potential vulnerabilities and they solutions. |
| 4 | |||
| 5 | 4 | Greg Burri | h2. Ban system |
| 6 | 1 | Greg Burri | |
| 7 | 4 | Greg Burri | In case of flooding from a peer, its IP can be banned for a period of time. If it recurs then the ban time is extended. |
| 8 | |||
| 9 | |||
| 10 | h2. A peer steals the peerID from an other peer. |
||
| 11 | |||
| 12 | h2. |
||
| 13 | |||
| 14 | |||
| 15 | h2. Flood of _IMAlive_ message |
||
| 16 | |||
| 17 | 2 | Greg Burri | h3. Problem |
| 18 | |||
| 19 | A peer can flood this message to a targeted peer with a different peerId for each message. |
||
| 20 | |||
| 21 | 1 | Greg Burri | h3. Solutions |
| 22 | 4 | Greg Burri | |
| 23 | If two many _IMAlive_ message are sent from the same IP then the peer is banned. |