reaver-wps-fork will not attempt Pixie or default Pin attacks regardless of parameters passed to it about reaver-wps-fork-t6x

[kcdtv]

Now you need to use -vvv (3 v) to have the "full" stdout with the hashes for pixiedust
-K might have been correctly executed with no positive results but - maybe - that was simply not stdouted at all.
Could you use -vvv instead of -vv to check that out?

[d8tahead]

I would assume that would be the solution to their problem, thanks kcdtv

[thesle3p]

same thing with -vvv it just brutes wps does not send hashes at all it
goes through the standard Reaver brute force. -W does not work either
Here is the args I am passing to reaver sudo reaver -i wlan1mon -b
-vvv -K 1 (or -W) -A -c and instead
of the Pixie loop or the default pin brute force it tries to dumb brute
the pin

On 07/07/2015 09:04 PM, kcdtv wrote:

Now you need to use -vvv (3 v) to have the "full" stdout with the hashes
for pixiedust
-K might have been correctly executed with no positive results but -
maybe - that was simply not stdouted at all.
Could you use -vvv instead of -vv to check that out?

—
Reply to this email directly or view it on GitHub
#25 (comment).

[thesle3p]

Can someone take a look at this? This was not the case until I updated to the latest version of reaver-wps-fork.

[kcdtv]

not before the 27 as i am not home, but i never had this issue. Maybe is due to the use of -A? Are yo correctly associated, could you post a sample of reaver stdout. cheers
🎱 this stupid emotiocone are realy the fucking best shit 🌗

[soxrok2212]

Try removing Reaver and pixiewps and reinstall them both, ensuring you have all of the dependencies. (Keep in mind that pixiewps has been updated to 1.2, and no longer requires libssl-dev). Not sure if this is the problem, but it has not been reported anywhere else so it might have just been an install/dependency issue.