![]() |
2012-08-21
, 16:07
|
|
Posts: 215 |
Thanked: 448 times |
Joined on Aug 2012
@ Burgas, Bulgaria
|
#752
|
Actually /home/opt and /opt are pointing to the same location. That is, it is the same file you just look at it from different links.
The Following User Says Thank You to tanago For This Useful Post: | ||
![]() |
2012-08-21
, 16:08
|
|
Posts: 1,648 |
Thanked: 2,122 times |
Joined on Mar 2007
@ UNKLE's Never Never Land
|
#753
|
I think I've found small glitch in Cleven's reaver implementation.
Using current command to invoke Cleven, after successful cracking of PIN, reaver x-term window just closes - without giving chance to actually verify found PIN or retrieved WPA PSK.
I've just checked it during real-test on my router, and reaver.db file *doesn't* keep retrieved WPA password (at least, using reaver from repositories, aka latest, compiled by Pali). Retrieved data is shown *only* on x-term window with cracking progress.
reaver have argument "-o" for providing output to file, but it prevents any info from appearing inside opened x-term window, where reaver is "working". Furthermore, using static path for -o, would result in further cracking attempts overwriting former ones.
IMO, it would be good idea to create new directory under /home/user/.cleven/keys, called - for example - wps (/home/user/.cleven/keys/wps). Then, some code in clevenHelper would read reaver's output, and react on "success" pattern, saving it (only relevant part, as whole log would be loooong) as retrieved WPS PIN and WPA PSK, vievable from "keys" tab from Cleven GUI.
What do you think, Saturn?
/Estel
The Following User Says Thank You to Saturn For This Useful Post: | ||
![]() |
2012-08-21
, 16:17
|
Posts: 43 |
Thanked: 16 times |
Joined on Mar 2010
|
#754
|
I think I've found small glitch in Cleven's reaver implementation.
Using current command to invoke Cleven, after successful cracking of PIN, reaver x-term window just closes - without giving chance to actually verify found PIN or retrieved WPA PSK.
I've just checked it during real-test on my router, and reaver.db file *doesn't* keep retrieved WPA password (at least, using reaver from repositories, aka latest, compiled by Pali). Retrieved data is shown *only* on x-term window with cracking progress.
reaver have argument "-o" for providing output to file, but it prevents any info from appearing inside opened x-term window, where reaver is "working". Furthermore, using static path for -o, would result in further cracking attempts overwriting former ones.
IMO, it would be good idea to create new directory under /home/user/.cleven/keys, called - for example - wps (/home/user/.cleven/keys/wps). Then, some code in clevenHelper would read reaver's output, and react on "success" pattern, saving it (only relevant part, as whole log would be loooong) as retrieved WPS PIN and WPA PSK, vievable from "keys" tab from Cleven GUI.
What do you think, Saturn?
/Estel
![]() |
2012-08-21
, 16:53
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#755
|
Can you delete the db file and re-run reaver?
you can put the correct pin as an option to make it find it immediately.
Maybe you have an old db structure or something.
PS: As I said I haven't tried it as I don't have the means and time.
At the moment I crack WPS with Cleven until the window closes (which means its cracked) then i have to open up a separate Xterminal window outside of Cleven and repeat the Reaver commands manually to finally get the password to stay on screen. Its a 10 second job but annoying
[+] Switching wlan0 to channel 6 [+] Restored previous session [+] Waiting for beacon from E0:69:95:3A:09:93 [+] Associated with E0:69:95:3A:09:93 (ESSID: 539) [+] Trying pin 12345678 [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [+] Sending EAPOL START request [+] Received identity request [+] Sending identity response [+] Received M1 message [+] Sending M2 message [+] Received M1 message [!] WARNING: Receive timeout occurred [+] Sending WSC NACK [!] WPS transaction failed (code: 0x02), re-trying last pin [+] Trying pin 10968550 [+] Sending EAPOL START request [+] Received identity request [+] Sending identity response [+] Received M1 message [+] Sending M2 message [+] Received M3 message [+] Sending M4 message [+] Received M5 message [+] Sending M6 message [+] Received M7 message [+] Sending WSC NACK [+] Sending WSC NACK [+] Pin cracked in 25 seconds [+] WPS PIN: '12345678' [+] WPA PSK: 'blablabla_blebleble_27' [+] AP SSID: 'test1
The Following User Says Thank You to Estel For This Useful Post: | ||
![]() |
2012-08-22
, 09:44
|
Posts: 81 |
Thanked: 36 times |
Joined on Aug 2011
@ Ahmedabad,India
|
#756
|
![]() |
2012-08-22
, 15:11
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#757
|
![]() |
2012-08-26
, 07:23
|
|
Posts: 59 |
Thanked: 16 times |
Joined on Jan 2012
|
#758
|
![]() |
2012-08-26
, 15:35
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#759
|
![]() |
2012-08-26
, 18:33
|
|
Posts: 59 |
Thanked: 16 times |
Joined on Jan 2012
|
#760
|
Packages: elGR Locale, SMSCON Editor, Swappolube, CSSU Features Configuration, Snuggle, YAMAS, Cleven
Garage: SMSCON, Swappolube, CSSU Features Configuration, Snuggle
Wiki: SMSCON, SMSCON Editor, Swappolube, CSSU Features Configuration, Cleven