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

Request #29

Open
peterpt opened this issue Jul 1, 2015 · 3 comments
Open

Request #29

peterpt opened this issue Jul 1, 2015 · 3 comments

Comments

@peterpt
Copy link

peterpt commented Jul 1, 2015

Is there anyway to configure wifite to use force -f on pixie wsp attack ?
the issue is that some networks pixie-wps can not crack them if -f option is not active .
an automated script on wifite could be usefull .
Something like this

If pixie-wps unable to get pin on normal cracking mode , then test "Brute force" option .
and then if brute force fails then starts the handshake capture like it usually do .

thanks for the changes in wifite .

@aanarchyy
Copy link
Owner

I will look into trying to add it, but i have no way to test it as i have no routers around me that give me the "--force" dialog.

@peterpt
Copy link
Author

peterpt commented Jul 6, 2015

dont worry , i have one router on my area that only with brute force works to retrieve the pin .
I can test it out here and send you the logs .
This in case if you agree .

@peterpt
Copy link
Author

peterpt commented Aug 18, 2015

any news about this ?
i was looking into the script , and if you could add this variable in the script
PIXIE_TIMEOUT = 660 # timeout for pixiewps attack
PIXIE_NOPSK = False # do not run reaver using pin found by pixiewps if it is sucessful
PIXIE_ONLY = False # only use pixiewps, do not run reaver brute-force
PIXIE_ADD_TO = 30 # add n seconds to timeout
PIXIE_BRUTE =True # use brute force

and adding the command somewhere in the script ( -f ) , this would be great .
I can get APS vulnerable to pixiewps , but i have to do the work all by hand , because wifite-ng does not do the brute force option .

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

2 participants