[Gzz-commits] storm/doc/pegboard/attacking_gisp--hemppah peg.rst

[Hermanni Hyytiälä]

CVSROOT:        /cvsroot/storm
Module name:    storm
Branch:         
Changes by:     Hermanni Hyytiälä <address@hidden>      03/06/06 08:10:07

Modified files:
        doc/pegboard/attacking_gisp--hemppah: peg.rst 

Log message:
        more twid

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/storm/storm/doc/pegboard/attacking_gisp--hemppah/peg.rst.diff?tr1=1.12&tr2=1.13&r1=text&r2=text

Patches:
Index: storm/doc/pegboard/attacking_gisp--hemppah/peg.rst
diff -u storm/doc/pegboard/attacking_gisp--hemppah/peg.rst:1.12 
storm/doc/pegboard/attacking_gisp--hemppah/peg.rst:1.13
--- storm/doc/pegboard/attacking_gisp--hemppah/peg.rst:1.12     Fri Jun  6 
07:56:24 2003
+++ storm/doc/pegboard/attacking_gisp--hemppah/peg.rst  Fri Jun  6 08:10:05 2003
@@ -5,8 +5,8 @@
 
 :Authors:  Hermanni Hyytiälä
 :Date-Created: 2003-06-05
-:Last-Modified: $Date: 2003/06/06 11:56:24 $
-:Revision: $Revision: 1.12 $
+:Last-Modified: $Date: 2003/06/06 12:10:05 $
+:Revision: $Revision: 1.13 $
 :Status:   Incomplete
 
 .. :Stakeholders:
@@ -16,8 +16,8 @@
 .. Affect-PEGs:
 
 This PEG document briefly describes the attack methods used by a "killer" 
-program against the GISP P2P software. The program is intended to be used
-to test GISP's robustness against hostile attacks.  
+program. The program is intended to be used to test GISP P2P software's 
+robustness against hostile attacks.  
 
 In this document we mean with "hostile peer" as an entity which is able to do 
a 
 (limited/simplified/modified) number of regular GISP peer's functionalies
@@ -40,19 +40,17 @@
 =================
 
 GISP does not appear to address the attacks against DHT systems
-described in Ref_1_ and Ref_2_.
-
-For determining whether GISP is resilient against hostile attack, 
-we want the answers to the following questions:
+described in ref1_ and ref2_. Using a simulation process as a 
+research method we want the answers to the following questions:
 
 - Does GISP have *obvious* exploits ?
 
 - If there are exploits how easily they can be used by an 
   hostile peer ? 
+  
+- How severe implications attacks may cause to GISP network ?
 
-- Is GISP resilient against (hostile) attacks or not ?
-
-- How severe implications attacks may cause ?
+- In general, is GISP resilient against (hostile) attacks or not ?
 
 - How well GISP is able to re-organise after a (hostile) attack ?
 
@@ -65,6 +63,13 @@
 
 - A hostile peer(s) doesn't reply to queries (a "dumb" peer)*
 
+.. Next you should describe the exact scenarios you want to try,
+   so start with the dumb peer and specify it exactly. Then run 
+   the test.
+   
+Scenario
+
+
 - A hostile peer(s) tries to drop certain packets/queries wilfully*
   
 - A hostile peer(s) forwards queries to incorrect destination peers
@@ -105,5 +110,5 @@
 codebase.
 
 
-.. _Ref_1: http://www.cs.rice.edu/Conferences/IPTPS02/173.pdf    
-.. _Ref_2: 
http://dcslab.snu.ac.kr/~buggy/p2p/paper/security/Pastry%20--%20Security%20for%20structured%20peer-to-peer%20overlay%20networks.pdf
+.. _ref1: http://www.cs.rice.edu/Conferences/IPTPS02/173.pdf    
+.. _ref2: 
http://dcslab.snu.ac.kr/~buggy/p2p/paper/security/Pastry%20--%20Security%20for%20structured%20peer-to-peer%20overlay%20networks.pdf