Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
blog.limos.fr
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Boris LONJON
blog.limos.fr
Commits
ad7a27a3
Commit
ad7a27a3
authored
7 years ago
by
mazenovi
Browse files
Options
Downloads
Patches
Plain Diff
fix ova ip
parent
04a647c4
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
content/Etudiants/zz2-f5-websec.md
+34
-38
34 additions, 38 deletions
content/Etudiants/zz2-f5-websec.md
with
34 additions
and
38 deletions
content/Etudiants/zz2-f5-websec.md
+
34
−
38
View file @
ad7a27a3
...
...
@@ -72,10 +72,10 @@ sous windows vous devrez peut être utiliser le path entier de vboxmanage
### Créer un réseau NAT
```
bash
vboxmanage natnetwork add
--netname
natwebsec
--network
"1
0.0.2
.0/24"
--enable
--dhcp
off
vboxmanage natnetwork add
--netname
natwebsec
--network
"1
72.16.76
.0/24"
--enable
--dhcp
off
```
### Télécharger les
ova
### Télécharger les
images OVA
voir
[
https://drive.mesocentre.uca.fr/d/69e5535b0b88425396d7/
](
https://drive.mesocentre.uca.fr/d/69e5535b0b88425396d7/
)
...
...
@@ -103,24 +103,24 @@ vboxmanage import kali.ova
vboxmanage import thenetwork.ova
```
### Mettre en place le port-forwarding sur
proxy
###
(optionnel)
Mettre en place le port-forwarding sur
debian
```
bash
vboxmanage natnetwork modify
--netname
natwebsec
--port-forward-4
"ssh:tcp:[127.0.0.1]:1337:[1
0.0.2.3
]:22"
vboxmanage natnetwork modify
--netname
natwebsec
--port-forward-4
"ssh:tcp:[127.0.0.1]:1337:[1
72.16.76.144
]:22"
```
### Se connecter en ssh
###
(optionnel)
Se connecter en ssh
```
bash
ssh
-p
1337 student@127.0.0.1
```
##
S
ur proxy et thenetwork
##
(fix) En cas de réseau injoignable s
ur proxy et thenetwork
si
```
bash
ping 1
0.0.2.4
# ping sur kali
ping 1
72.16.76.145
# ping sur kali
```
renvoie
...
...
@@ -135,7 +135,7 @@ vérifier le numéro de votre interface réseau
student@proxy:~
$
ifconfig
-a
eth2 Link encap:Ethernet HWaddr 08:00:27:ae:b5:20
inet adr:1
0.0.2.
3 Bcast:1
0.0.2
.255 Masque:255.255.255.0
inet adr:1
72.16.76.14
3 Bcast:1
72.16.76
.255 Masque:255.255.255.0
adr inet6: fe80::a00:27ff:feae:b520/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:24 erreurs:0 :0 overruns:0 frame:0
...
...
@@ -157,7 +157,7 @@ par exemple ce numéro peut être eth2 (comme ci dessus) au lieu de eth0
il faut alors modifier le fichier /etc/network/interfaces en fonction
```
```
bash
student@proxy:~
$
sudo
vi /etc/network/interfaces
# This file describes the network interfaces available on your system
...
...
@@ -168,57 +168,49 @@ auto lo
iface lo inet loopback
# The primary network interface
auto eth0
# iface eth2 inet dhcp
iface eth0 inet static
address 10.0.2.3
auto eth2
iface eth2 inet static
address 172.16.76.143
netmask 255.255.255.0
gateway 1
0.0.2
.1
gateway 1
72.16.76
.1
```
puis activer l'interface réseau
```
```
bash
student@proxy:~
$
sudo
ifup eth2
```
réessayer
```
ping 1
0.0.2.4
# ping sur kali
```
bash
ping 1
72.16.76.145
# ping sur kali
```
Ce bug est dû à la numérotation fantaisiste d'Ubuntu des interfaces réseau ...
##
# /etc/hosts FYI
##
liste des vms / noms de domaine
```
10.0.2.1 us.er
# SecLab
172.16.76.143 proxy secured heart.bleed fo.ol #proxied version of dum.my
10.0.2.2 debian
10.0.2.2 mutillid.ae good.one go.od targ.et
10.0.2.2 dvwa.com dv.wa
10.0.2.2 good.one go.od targ.et d.oc dum.my
10.0.2.2 drup.al hackable-drupal.com drupal
10.0.2.2 wordpre.ss bl.og wp wordpress
10.0.2.2 spip sp.ip
172.16.76.144 good.one go.od targ.et
172.16.76.144 mutillid.ae
172.16.76.144 dvwa.com dv.wa
172.16.76.144 d.oc
172.16.76.144 dum.my
172.16.76.144 drup.al hackable-drupal.com drupal
172.16.76.144 wordpre.ss bl.og wp wordpress
172.16.76.144 spip sp.ip
172.16.76.145 bad.guy hack.er 1337.net
10.0.2.3 proxy
10.0.2.3 secured heart.bleed fo.ol
172.16.76.142 thenetwork
10.0.2.4 kali
10.0.2.4 bad.guy hack.er 1337.net
10.0.2.5 thenetwork
172.16.76.1 us.er
```
### see also
*
[
make your own sec lab
](
http://mazenovi.github.io/blog/2015/11/10/make-your-own-sec-lab/
)
*
[
faire son propre seclab
](
http://blog.mazenod.fr/faire-son-propre-seclab/
)
## Evaluation
*
Examen écrit en fin de session (/10)
...
...
@@ -239,3 +231,7 @@ Ce bug est dû à la numérotation fantaisiste d'Ubuntu des interfaces réseau .
* [vincent.mazenod@isima.fr](mailto:vincent.mazenod@isima.fr)
* ```[TP websec]``` dans le sujet du mail ... sinon je vous perds ;)
## See also
*
[
faire son propre seclab
](
https://blog.mazenod.fr/faire-son-propre-seclab.html
)
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment