Open GoogleCodeExporter opened 8 years ago
I suggest you check the keys this way. Make a short dictionary file with the
WPA keys you got thru reaver. Using airodump-ng and aireplay-ng capture a WPA
handshake from your target. Run aircrack-ng against the handshake using the
small dictionary file and see if it is the key. Deauth a client that is
actually connected to the net. If you see alot of data movement in airodump-ng
that is a good sign.
In this way you can prove that it is or is not the key.
Original comment by muske...@yahoo.com
on 3 Aug 2012 at 2:03
If you are having problem with your hard drive installation or operating system
here is an easy solution.
We loaded BT5R2 to a 8 gig flash drive. Flash drive divided into 3gig fat32 and
4 gig ext3. We changed the syslinux.cfg so the flash drive would exhibit
persistance.
We booted the computer from the flash drive and then connected to the internet
thru wicd via an RTL8187 USO36H wireless reciever
We typed
apt-get update.
Note wash and reaver already installed in BTR2
Then ran wash got our targert and then ran reaver against the closest router we
could find. The RSSI on the router was -39. It started to crack the router.
We then picked a router with an RSSI of -72. The reaver program went round and
round similiar to your post. Remember reaver works poorly when the RSSI is
below 50.
Original comment by muske...@yahoo.com
on 3 Aug 2012 at 9:12
If you are having problem with your hard drive installation or operating system
here is an easy solution.
We loaded BT5R2 to a 8 gig flash drive. Flash drive divided into 3gig fat32 and
4 gig ext3. We changed the syslinux.cfg so the flash drive would exhibit
persistance.
We booted the computer from the flash drive and then connected to the internet
thru wicd via an RTL8187 USO36H wireless reciever
We typed
apt-get update.
Note wash and reaver already installed in BTR2
Then ran wash got our targert and then ran reaver against the closest router we
could find. The RSSI on the router was -39. It started to crack the router.
We then picked a router with an RSSI of -72. The reaver program went round and
round similiar to your post. Remember reaver works poorly when the RSSI is
below 50.
Original comment by muske...@yahoo.com
on 3 Aug 2012 at 9:12
Original issue reported on code.google.com by
heartbla...@gmail.com
on 2 Aug 2012 at 10:34