deterlab
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| deterlab [2017/05/17 09:04] – created silvio.biagioni@unitn.it | deterlab [2021/01/29 10:58] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| + | |||
| + | ===== Requirements ===== | ||
| + | This exercise requires basic OS and networking knowledge, understanding of Denial of Service (DoS) and buffer overflows. It also involves coding skills. It can be done in introductory and advanced security classes. | ||
| + | |||
| + | |||
| + | ===== Setup ===== | ||
| + | Before the exercise you need to perform the following steps: | ||
| + | - Create groups of students in your class project on DETERLab, one group per attack team. Give to the groups easily related names (e.g., " | ||
| + | - Swap in the experiment using the related NS file: <code bash> / | ||
| + | - For each topology created, remove access to the three //client// machines for all but their attack team, and remove access to //server// and //gateway// machine for all but the automated defense team. Remove also the access to //router// for all teams. These steps can be done by running the '' | ||
| + | exp1-attack-group exp1-defense-group exp2-attack-group exp2-defense-group </ | ||
| + | |||
| + | < | ||
| + | |||
| + | In this specific case, we declare in the first line the experiment ID, and the list of the respective attack and defense groups. Therefore, the experiment '' | ||
| + | |||
| + | <REPLY END: THE LAST STEP IS NOT CLEAR. WHICH IS THE SEMANTICS OF THE SECOND LINE?> | ||
| + | |||
| + | This step will ensure that during exercise team members cannot log into machines controlled by the opposing team and spy on them. | ||
deterlab.1495004643.txt.gz · Last modified: (external edit)
