Open GoogleCodeExporter opened 9 years ago
[deleted comment]
Have tried with the Actual Pin(the correct pin) still get the same response
from reaver.
Somehow router will not reply with M3 response.
Original comment by TaoWarri...@gmail.com
on 24 Aug 2012 at 10:10
I've got the same problem on dlink dir615 firmware version 7.17.any updates on
this?
Original comment by k...@jedi.my
on 15 Jan 2014 at 3:10
This started happening since the last upgrade of the DIR-615 firmware. An
option in the wireless settings called lock security settings is turned on by
default and this blocks any cracking activity by reaver. the attack works once
you disable that option.
Original comment by 10alph...@gmail.com
on 16 Feb 2014 at 2:22
This is to follow up with my earlier reported issue.
Is been a while since my last use of reaver. Few days ago, I use reaver to test
on all my neighbour router. It seems all the new router already block reaver.
Since reaver has been FAMOUS cracking WPS.
I found the new router Aztech, TP-Link, D-Link, etc has update thier router
security, either stoping reaver to crack or even implement router lock state
and cost u give up for cracking.
So I restudy the WPS and WPA on both REAVER code and AIRCRACK code. and I found
out a new method that may able to crack 50%-60% router.
Yesterday I have crack a router with WPS DISABLE ROUTER(WPA2-AES) only with
less than 40 minutes. Tonight will try other router! there are about 30 router
nearby my house!
*REAVER did give me a good time, but REAVER is no longer workable in realworld,
pls prove me wrong!
*If my method are able to crack up to 60% of all the router then is proven
REAVER is much slower than my method, based on my calculation, my method will
use 120 minutes max to crack a router.
Original comment by TaoWarri...@gmail.com
on 1 Apr 2014 at 3:36
Tao, do you have any other results for your method? would you share it?.
Original comment by bonazzi...@gmail.com
on 20 May 2014 at 5:20
Tao would you share your method?
Original comment by jorgepal...@gmail.com
on 8 Nov 2014 at 12:47
Original issue reported on code.google.com by
TaoWarri...@gmail.com
on 24 Aug 2012 at 7:51