search

sensepost / hostapd-mana

SensePost's modified hostapd for wifi attacks.
https://w1f1.net/
Other
547 stars 129 forks source link

Can't capture hashes #6

Open jsevilleja opened 8 years ago

jsevilleja commented 8 years ago

Hi,

when trying the latest commit, I get the identity of the user which is connecting, but not its challenge/response hash. I can get this information with hostapd-wpe or an old commit of hostapd-mana (can't remember which one, but I know that its configuration was still using "karma" instead of "mana" for enabling the karma attacks). What am I missing / what should I do to get this behaviour again? Thanks.

singe commented 8 years ago

Would you be open to sharing the output, pcaps and your config with me to try debug?

jsevilleja commented 8 years ago

No problem. However, I've edited the output to eliminate the networks I don't own.

The configuration I use on the phone is:

ssid -> eduroam peap with mschapv2

hostapd-mana.zip

singe commented 6 years ago

Ok, what it looks like is happening is hostapd can't negotiate PEAP based on the config in your hostapd.eap_user file. You can see it in the output from hostapd's output in:

wlan0: STA 64:bc:0c:29:ed:d2 IEEE 802.1X: authentication failed - EAP type: 0 ((null))
wlan0: STA 64:bc:0c:29:ed:d2 IEEE 802.1X: Supplicant used different EAP type: 25 (PEAP)

Can you try the latest version of hostapd-mana (you'll need to change your config a little ala https://github.com/sensepost/hostapd-mana/wiki/MANA-EAP-Options-(aka-WPE)) Can you also post your hostapd.eap_user file?