Quote "we bounced the user off their own AP, and now when they re-authenticate, airodump-ng will attempt to grab their password in the new 4-way handshake."


what to do to stop users on my network from getting bounced and get the deauth ?

use longer security keys with WPA2 and AES ciphers. It was compromised for shorter keys

Quote "we bounced the user off their own AP, and now when they re-authenticate, airodump-ng will attempt to grab their password in the new 4-way handshake."


what to do to stop users on my network from getting bounced and get the deauth ?

Um, no.

airodump-ng WILL grab the 4-way handshake NOT the password. you can then use that for way handshake to do create a hash of dictionary passwords then using memory-time trade off, if you're hardware is fast, you can do brute force quicker. It still doesn't garuntee anything. wpa/wpa2 is not cracked like WEP. If you want to know more than why don't you test it and see if it gives you the password, it wont because it cant

use longer security keys with WPA2 and AES ciphers. It was compromised for shorter keys

how long ?!

and how to do it ?


can you give me an example please.

just take a router and set up wifi pre-shared key for WPA2/AES and check how long it takes for you to crack it.

Minimal length is 8 symbols. So, you can list what GPU you used to get that key from sniffed data or whatever and increase symbol count when you have gotten hold of the current key.

also, use of rainbow tables for password guessing is powerful tool. but there are always 10% to 20% of passwords that are not guessed in 1 month - nobody is bothering guessing those. If you have 5M of them and 1M is not known (at maximum) - who cares. So you can construct safe password.