Merge pull request #619 from jackieklaura/fix/safer-docker-port-mapping

fix: use safer default for docker port mapping

README.id.md

@@ -300,14 +300,14 @@ Sebagai contoh, Anda dapat mengubah
 
 ```
 ports:
-  - 4280:80
+  - 127.0.0.1:4280:80
 ```
 
 Menjadi
 
 ```
 ports:
-  - 8806:80
+  - 127.0.0.1:8806:80
 ```
 
 DVWA sekarang dapat diakses di `http://localhost:8806`.

README.md

@@ -335,18 +335,24 @@ For example, you can change
 
 ```yml
 ports:
-  - 4280:80
+  - 127.0.0.1:4280:80
 ```
 
 to
 
 ```yml
 ports:
-  - 8806:80
+  - 127.0.0.1:8806:80
 ```
 
 DVWA is now accessible at `http://localhost:8806`.
 
+In cases in which you want DVWA to not only be accessible exclusively from your own device, but
+on your local network too (e.g. because you are setting up a test machine for a workshop), you
+can remove the `127.0.0.1:` from the port mapping (or replace it with you LAN IP). This way it
+will listen on all available device. The safe default should always be to only listen on your
+local loopback device. After all, it is a damn vulnerable web application, running on your machine.
+
 #### DVWA auto starts when Docker runs
 
 The included [`compose.yml`](./compose.yml) file automatically runs DVWA and its database when Docker starts.

compose.yml

@@ -19,7 +19,7 @@ services:
     networks:
       - dvwa
     ports:
-      - 4280:80
+      - 127.0.0.1:4280:80
     restart: unless-stopped
 
   db: