Changes between Version 46 and Version 47 of ExDescLang

Timestamp:

Oct 18, 2010 2:31:31 PM (14 years ago)

Author:

sunshine

Comment:

--

ExDescLang

@@ -74 +74 @@
 === Experiment design ===
 
-Now I'm a user who wants to design my experiment. I need to combine two metadescriptions and somehow tie them down to generator choices. To combine I need to specify how outputs of worm metadescription match inputs of P2P metadescription. I'll do this visually here:
+Now I'm a user who wants to design my experiment. I need to combine two metadescriptions and somehow tie them down to generator choices. To combine I need to specify how outputs of worm metadescription match inputs of P2P metadescription. I'll do something like this:
 
    [[Image(wp2pcomb.jpg)]]
@@ -150 +150 @@
    Nothing in addition to the topology and timeline above.
 
+=== Experiment design ===
+
+Now I'm a user who wants to design an experiment. I need to combine two metadescriptions (DNS cache poisoning and phishing) and somehow tie them down to generator choices. To combine I'll do something like this:
+
+   [[Image(wp2pcomb.jpg)]]
+
+i.e. each infected host becomes a peer.
+
+The system now needs to offer me several generators:
+
+ * It should offer a topology generator and map the initial infected set, vulnerable set and leader set to the topology that gets generated.
+ * It should offer event generator for each of the events: scan, yespeer, wannapeer, leaderis, hello, cmd and report. Specifically for scan, yespeer, wannapeer, hello, cmd and report it should offer traffic generators.  For leaderis it could either offer a traffic generator or an option to hardcode the leader ID into the peer software.
+ * It should offer a malware generator for vulnerability x
+
+User either chooses each generator or agrees to use a default one for each choice. User can then manipulate the generators (their parameters) and the workflow. For example the user may add "patched" state after the "infected" one with the "patch" event to make the transition.
+
 = TODO =