Всем привет!Кто-то делал ето (Hopefully this helps out any future wanderers who recover a PIN w/reaver but no PSK, as I have had this happen a few times myself with different testing devices and firmwares.

I am not 100% certain why this occurs, but I have a feeling that there’s more than one reason behind it. Regardless, it's important to know that you CAN authenticate to the AP with just the pin, and in many cases, you will be able to recover that sessions PSK, albeit a manual processes.

I use debian squeeze (6.0), with kernel 3.2.0-0 from backports, along with latest compat-wireless (3.3.1). I have tested this with wpa_supplicant from the repos (v0.6.10), and not from source.

First, set yourself up a very basic wpa_supplicant.conf in /etc/wpa_supplicant.conf:

--

ctrl_interface=/var/run/wpa_supplicant

ctrl_interface_group=0

update_config=1

--

Second, start wpa_supplicant in daemon mode:

wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf –B

Third, run wpa_cli, and verify that it's working by issuing command 'status'. You should see wpa_state=INACTIVE

Fourth, lets add our BSSID and PIN:

wps_reg xx:xx:xx:xx:xx:xx 12345678

You should see an "OK". Wait a few more seconds as wpa_supplicant picks up the BSSID and tries to associate and perform key negotiation. What you want to see is "CTRL-EVENT-CONNECTED", which will indicate that the PIN was accepted and that you're now associated.

At this point, if you were to exit wpa_cli, you could run dhclient on wlan0 and would be offered an IP from the AP, assuming DHCPd were enabled.

Go ahead and type the command 'save', which should output another "OK". This will update the wpa_supplicant.conf file, as specified from the command line, with a static configuration for this new network.

Verify by: cat /etc/wpa_supplicant.conf

If all went well, you should have a line under this new network titled 'psk'.

Good luck!

я вот два раза уже пробывал но не выходить не как!