WPA PSK Key Found - Githubissues

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. Key cracked
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
BT5 Rtl8187L

Please provide any additional information below.
I cracked the pin but after that What will i do? What is wireless Key?

[!] WARNING: Receive timeout occurred
[+] Key cracked in 31727 seconds
[+] WPS PIN: '99408909'
[+] WPA PSK: '6B545620600E5333DB2A52EDCAC68C2AE45F4F1054BF14937C9D1A731B3DBA47'
[+] AP SSID: 'Network-74ea3ac80256'

I triyed this " 
6B545620600E5333DB2A52EDCAC68C2AE45F4F1054BF14937C9D1A731B3DBA47 " - "99408909" 
but I cant connected Pls help me....

Original issue reported on code.google.com by burakozy...@gmail.com on 5 Jan 2012 at 4:11

GoogleCodeExporter commented 8 years ago

If you are testing this on your own router, you should have no problems 
connecting to it, no? Unless I'm missing something...

Original comment by philippe...@hotmail.com on 5 Jan 2012 at 4:14

GoogleCodeExporter commented 8 years ago

It has been found that some APs don't return the existing WPA key, but instead 
generate a new one that is returned to the registrar (presumably so that the 
registrar can then configure the AP with this new random WPA key). This is not 
something that Reaver can control AFAIK (there is an option in the WPS exchange 
that is supposed to tell the AP to not do this, but some seem to ignore it). 

This could be the issue in your case; of course, that WPA key could also be the 
correct one, there's no way for me to know. Either way, Reaver is functioning 
properly.

Original comment by cheff...@tacnetsol.com on 5 Jan 2012 at 4:28

Changed state: Invalid

bngmc / reaver-wps

WPA PSK Key Found #89