WPA PSK

[GoogleCodeExporter]

All of the networks I have been testing reaver on, gives me the WPS PIN CODE 
but the WPA-PSK is never been decrypted:

Example:
[+] WPS PIN: '65915646'
[+] WPA PSK: '49ed453a190259497ab2d16009e543ab6c7a0b3594c1b658799161f6fe3bf57a'

I thought the idea of reaver was it gona get the decrypted password of the 
WPA-PSK aswell?

Original issue reported on code.google.com by rohedl...@gmail.com on 13 Jan 2012 at 9:19

[GoogleCodeExporter]

I've seen that a few times too. That is the PSK the router is giving Reaver.

I think that some routers are configured to generate a random key if WPS hasn't 
been used before.

Original comment by dgprat...@gmail.com on 13 Jan 2012 at 11:23

[GoogleCodeExporter]

I guess it's the same issue as here:
http://code.google.com/p/reaver-wps/issues/detail?id=138#makechanges

WPA is maybe disabled

Original comment by andremeg...@hotmail.com on 14 Jan 2012 at 12:31

[GoogleCodeExporter]

Thanks for the feedback, guys! Maybe there is some workaround of this issue, to 
force the router somehow.

Original comment by rohedl...@gmail.com on 14 Jan 2012 at 10:14

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

it's same as issue 25 and issue 108.

Original comment by s...@lubie.net on 14 Jan 2012 at 1:24

[GoogleCodeExporter]

It looks like this issue just won't go away.  I agree that it should not be 
"fixed" by any change that would detract from the information that the router 
returns, but it would be helpful if some clarification could be added to 
reaver's output.

Example:
[+] WPS PIN: '65915646'
[+] WPA PSK: '49ed453a190259497ab2d16009e543ab6c7a0b3594c1b658799161f6fe3bf57a'
[+] WPA encryption is disabled.  This 63 byte WPA PSK may be router-generated.

Original comment by kbus...@gmail.com on 14 Jan 2012 at 2:40

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

"With the PIN method, all devices are associated with a unique number printed 
on the device or its packaging, or displayed on the device's LCD panel or 
screen. To enroll a device, its PIN is entered into a "WPS registrar" – 
usually a configuration page on the AP, gateway or controller. The registrar 
and device complete a secure over-the-air WPS handshake, during which the 
registrar assigns a random PSK to the device. The device then self-enables 
WPA2-PSK, using those WPS-supplied SSID and PSK values."

http://rpc.one.pl/pliki/openwrt/backfire/10.03.x/atheros/hostapd/dokumentacja/RE
ADME-WPS

seems random psk can be used on some ap devices during pin wps setup and it's 
in specs. question is why psk obtained with this method is rejected during wpa 
authorization (wpa is enabled on ap)? maybe during pin setup reaver introduce 
us somehow to ap (kept there with random psk pair) and during regular 
wpa_supplicant/wicd we are introduced other way? it's just a guess coz i 
haven't check traffic logs yet.

Original comment by s...@lubie.net on 14 Jan 2012 at 10:07

[GoogleCodeExporter]

This is a router-specific "feature". There have been reports of some routers 
exhibiting this behavior, and it is unclear if they do it only if WPA is not 
configured or not. It is expected however that the operator at least knows the 
type of encryption used on the wireless network he is targeting.

@sebo: Reaver does not target the PIN method; this is a common misunderstanding 
I'm afraid. The PIN method is used for adding devices to a WPS network, and 
requires user interaction on the part of the network owner. Reaver targets the 
registrar functionality of WPS, which, despite also using a PIN for 
authentication, is actually the exact opposite of the PIN method used to add 
devices to the network.

Original comment by cheff...@tacnetsol.com on 15 Jan 2012 at 5:58

[GoogleCodeExporter]

Hello there your work is  a master piece however i would like to ask you 
something, if i have a old router would it the program still try to bruteforce 
a router?, can u not create something that is able to detect if the router 
supports wps or not it will be must easy, my idea was to track the product via 
mac address of the year of the model that it was created example if 00:34 was 
created since 2 years ago therefore it will the program will be able to detect 
that its a new router that can support wps, please tell me if your code was 
able to detect if the router has wps or not thanks

Original comment by leacocks...@gmail.com on 24 Jan 2012 at 7:48

[GoogleCodeExporter]

Leacocks: There is already there: walsh that comes with reaver will show you if 
the router has WPS/supported/activated. Example: "walsh -i mon0 --scan"

Original comment by rohedl...@gmail.com on 24 Jan 2012 at 9:30

[GoogleCodeExporter]

Issue 179 has been merged into this issue.

Original comment by cheff...@tacnetsol.com on 24 Jan 2012 at 10:45

[GoogleCodeExporter]

so can someone make guide how to fix this? i got the wpa pin but keeps on 
giving me random 64 hexa digits.. someone help plz.. what next to do to obtain 
network key?

Original comment by redle...@gmail.com on 7 Feb 2012 at 2:53

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

gcarvalho5 > how u use wpa_supplicant to connect with WPS PIN and not 
reconfigure router device? it is possible anyway? show some conf :)

Original comment by kont...@pkt.poznan.pl on 11 Feb 2012 at 2:50

[GoogleCodeExporter]

This happened to me but I was able to get the ASCII key by re-running reaver 
and loading the previous session; the WPS pin was tested again and it worked.

Original comment by filthst...@gmail.com on 14 Mar 2012 at 5:42

[GoogleCodeExporter]

Check out https://code.google.com/p/reaver-wps/issues/detail?id=203

Original comment by ryanjna...@gmail.com on 13 Apr 2012 at 5:33

[GoogleCodeExporter]

I had the same hash send to me after cracking the PIN/.
I just booted up windows. Opened the control panel and started to Setup a new 
router. The windows menus asked for the PIN and generated a new WPA PSK. 
If you stumble upon this situation, generate a new key. Chances are that the 
router's owner is not using the WiFi. This was my case. I went to him and 
checked :). OR if he is using it, by resetting it you will make the router's 
owner to change and define a new PSK key. And you will have the PIN to obtain 
the new PSK key :)
Router was TP-LINK WR740N with untouched default factory settings on the WiFi. 
Cheers/.

Original comment by BHT...@gmail.com on 3 Jun 2012 at 1:55

[GoogleCodeExporter]

hola  mola

Original comment by loepreet...@gmail.com on 8 Oct 2013 at 10:22

[GoogleCodeExporter]

#26 BHT...@gmail.com
I had the same hash send to me after cracking the PIN/.
I just booted up windows. Opened the control panel and started to Setup a new 
router. The windows menus asked for the PIN and generated a new WPA PSK. 
If you stumble upon this situation, generate a new key. Chances are that the 
router's owner is not using the WiFi. This was my case. I went to him and 
checked :). OR if he is using it, by resetting it you will make the router's 
owner to change and define a new PSK key. And you will have the PIN to obtain 
the new PSK key :)
Router was TP-LINK WR740N with untouched default factory settings on the WiFi. 
Cheers/.

WHAT WPS PIN GOT?

Original comment by b-a-c-k-...@outlook.com on 17 Apr 2014 at 12:36

[GoogleCodeExporter]

This happens usually with TP-link routers. If you got hash-like WPA-PSK, you 
should download TP-Link QSS utility. Install it and you will have option in it 
to enter pin. Enter pin and you will be connected to AP. Then you should get 
access to router's settings and change settings to settings which was before 
you entered PIN(e.g. SSID, wpa password).

Original comment by Demon...@gmail.com on 11 Jun 2014 at 2:41