This repository has been archived on 2025-04-28. You can view files and clone it, but cannot push or open issues or pull requests.
netsec-djw2/hw3/hw3.md
David Westgate 4cda1ad869 hw3 progress
2024-05-09 18:33:31 -07:00

45 lines
1.6 KiB
Markdown

# Homework 3: Cracking WiFI!
## Crack the NetSec WiFi network password with bettercap
### Find the BSSID and connected client of the NetSec Network
### Perform a deauth attack on the network with bettercap and capture the 4-way handshake
### Use the hcx toolsuite to convert the captured handshake to a format that hashcat can understand
### Crack the password using hashcat and rockyou.txt
### Connect workstation to the wifi network and show using nmtui
Now that I have found the password, I can initiate a wifi connection from `mallory` to the raspberry pi
The first issue encountered was the the network manager was inactive. This is confirmed by running `systemctl status NetworkManager`
![network-manager](./network-manager-status.png)
This was fixed by running `sudo systemctl start NetworkManager`
Now with `sudo nmtui` I can finally attempt connect to NetSec with the password, `crackme1`.
![nmtui-connect](./nmtui-connect.png)
The connection was successfull
![nmtui-connected](./nmtui-connected.png)
## Scan the network with nmap
I now want to scan the network to identify the router, and devices connected to the router. A quick check with `iwconfig` and looking at the `wlan0` interface shows that as a client of this router, we are in the subnet `192.168.0.0/24`
![subnet](./subnet.png)
Now running `sudo nmap -sn 192.168.0.0/24` (a simple ping scan) we have some interesting results.
![nmap](./nmap.png)
### Open ports and services on client 1
### Open ports and services on client 2
### Access the RTSP stream
#### Screenshot
#### Camera make, model, brand, capacity, and manufacture date