Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WPA Sycophant freezes #1

Open
Lexus89 opened this issue Aug 20, 2018 · 4 comments
Open

WPA Sycophant freezes #1

Lexus89 opened this issue Aug 20, 2018 · 4 comments

Comments

@Lexus89
Copy link

Lexus89 commented Aug 20, 2018

Sometimes after grabbing the first identity it seems to go okay, even though i get eap auth failed. After that when it grabs another identity it displays the identity in form of many underscores and some other chars (so far always string length of 7) and freezes. When waiting a while MANA gets stuck too when checking for the sycophant state file. When killing the sycophant process hostapd-mana proceeds again. Having a hard time identifying where it goes wrong exactly.

@singe
Copy link
Collaborator

singe commented Aug 21, 2018

The freeze is because of the way @cablethief does the usleep to prevent thrashing while mana grabs details. I've seen it.

You will see an auth failure on the legit client/supplicant because passing the EAP success from the legit AP isn't implemented yet.

But you should see the identity. Can you send me all the debugging info? Your hostapd-mana config, eap_user file and invocation. Likewise your wpa_sycophant config and invocation. Then lastly the legit AP and client details (device type & OS and how you legit connect like a screenshot of the config).

@Lexus89
Copy link
Author

Lexus89 commented Aug 21, 2018

I'm seeing auth failed at the wpa sycophant supplicant but i indeed get the identity (only first time). I will have a look what info i can get you (company AP..).

@GithubKillsMyOpsec
Copy link

GithubKillsMyOpsec commented Oct 26, 2020

I also am having the same issue
I believe it might have something to do with the wpa_supplicant

@cablethief
Copy link
Member

I also am having the same issue
I believe it might have something to do with the wpa_supplicant

How are you running it? Can I see your config files?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants