HaKRB0y / reaver-wps

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

The 99.99% Problem has Returned in Sep-Nov 2013 #586

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
We have noted previously that Reaver would run up to 99.99% and go into an 
enless loop. We solved it in 2012 by reverting to Reaver 1.3 and an alteration 
to the script was suggest(not by us) in these blogs.

The problem has returned in Nov 2013. We are using the latest Reaver in 
kali-linux. We have had five cases on two different computers in different 
areas. Other in Sept 2013 onward have noted this. We are trying the soltions of 
script change and Reaver 1.3 but we think this is something new.

Original issue reported on code.google.com by tuispl...@gmail.com on 29 Nov 2013 at 8:41

GoogleCodeExporter commented 8 years ago
An alternate solution to this problem might be in using bully an alternative 
WPS cracking program to reaver. Bully has the option to bruteforce last 
checksum digit of PIN. It seems like a possible solution for this problem until 
reaver incorporates this option in the command line. You can follow the 99.99% 
problem in kali-linux forums as both bully and reaver are intigrated into the 
kali-linux package and can be updated easily with apt-get install reaver or 
apt-get install bully

Original comment by tuispl...@gmail.com on 3 Dec 2013 at 12:08

GoogleCodeExporter commented 8 years ago
Against our first router that showed the 99.99% problem - kali-linux using 
Reaver 1.4-2kali7 cracked the code. 

Original comment by tuispl...@gmail.com on 3 Dec 2013 at 6:17

GoogleCodeExporter commented 8 years ago
guys , pleaseee help me :(((
i install bully and do commands right !
but i get this ! :

root@Max:~# bully -b xx:xx:xx:xx:xx:xx -c 6 -T  mon0
[!] Bully v1.0-22 - WPS vulnerability assessment utility
[+] Switching interface 'mon0' to channel '6'
[!] Using '00:11:22:33:44:55' for the source MAC address
[+] Datalink type set to '127', radiotap headers present
[+] Scanning for beacon from '60:a4:4c:ee:cd:a4' on channel '6'
[!] Excessive (3) FCS failures while reading next packet
[!] Excessive (3) FCS failures while reading next packet
[!] Excessive (3) FCS failures while reading next packet
[!] Disabling FCS validation (assuming --nofcs)
[+] Got beacon for 'milk' (xx:xx:xx:xx:xx:xx)
[X] The AP doesn't appear to be WPS enabled (no WPS IE)

Help me :(

Original comment by pooya.si...@gmail.com on 29 Sep 2014 at 4:58