quadcore1 / reaver-wps

Automatically exported from code.google.com/p/reaver-wps
0 stars 0 forks source link

faster way to speed up the bruteforce attack?Using GPU #331

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Hi,
Does in any way reaver can support bruteforce attack using GPU to speed up the 
process in the future?

Original issue reported on code.google.com by selfd...@gmail.com on 14 Jun 2012 at 3:37

GoogleCodeExporter commented 8 years ago
The hardware limiting factor in Reaver is the target Access Point (AP). As long 
as you have a good wireless connection/close proximity to the AP, Reaver will 
work as fast as the AP will let it. The vulnerability is in how the AP responds 
to the 8 digit pin (technically two separate four digit pins combined into one 
eight digit pin). There isn't a four-way handshake to capture and attack 
offline, you physically have to communicate with the AP over wireless.

Original comment by jeffd...@gmail.com on 15 Jun 2012 at 9:42

GoogleCodeExporter commented 8 years ago
Yeah i noticed that we have to run the attack while the AP is 'on' ,
The fastest i can get for now  is abt 4/5 seconds/pin...is there any way to 
make it faster?
Im running bt5 in vm btw...
Thanks 4 ur reply :)

Original comment by selfd...@gmail.com on 16 Jun 2012 at 5:31

GoogleCodeExporter commented 8 years ago
The attack is completely different from Bruteforcing the PSK the old method 
which is done offline (by using all the power of CPU and all the GPUs to find a 
PSK that fits). Reaver sends the PINs, the router and the quality of connection 
are the bottleneck here. 

Original comment by nexdem...@gmail.com on 18 Jun 2012 at 9:10

GoogleCodeExporter commented 8 years ago
so how can we send faster pins? 

Original comment by eminciha...@gmail.com on 27 Jan 2013 at 1:22

GoogleCodeExporter commented 8 years ago
I want to bump this thread. I have been working on an AP for days now with 
~ATH9K laptop wireless card. Getting anything from 9 sec/p to 17 sec/p and a 
5min wait every 10-20 pin attempts due to gateway limiting. Also using -d 0 -c 
# --ignore-locks and every other suggestion out there. Have my laptop setup 
with almost line of sight (5m) to the AP (maybe 1 brick wall/window) and still 
running as mentioned above.

I am seriously starting to think that for Reaver to work effectively, you need 
to be in the same room as the AP. In which case you can save yourself the PAIN 
and go over and get the WPS off the back of the unit! haha

Sorry for being a smart a$$ but it just seams that way! 

Original comment by samwh...@gmail.com on 26 Jun 2013 at 11:00