You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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)
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.
The text was updated successfully, but these errors were encountered: