#Wpa2 hash decoder crack#

People are welcome to try to crack my key. Such a passphrase makes it very unlikely that a PSK cracking attack will work. In that case, use a long sentence/passphrase, with punctuation, spaces, etc. But people don't like long hex PSKs, and like to use something that a human can remember. Length of the PSK is the most important factor - ideally you should configure a long PSK in hex for the best possible strength. If a customer wants a response from Aruba, our consistent response over the past 15 years has been 'Use a strong PSK'. If you have a weak PSK, your network is vulnerable to having an attacker discover the PSK. The fundamental security issue here is the use of a weak PSK. The new attack makes it possible to do the attack without needing a client to observe, so it makes the attack more efficient. To capture the 4-way handshake you could either wait for a client to show up, or you could deauth a currently-connected client and watch it reassociate. I'm not sure that we'll write up anything formal on this - there have been a large number of attacks against WPA2-PSK over the years and this isn't fundamentally anything new that changes the security story.ДЇor those who don't want to dig into the details - previously to attack WPA2-PSK you needed to capture a client doing a 4-way handshake, and then you could brute force or dictionary attack the PSK. We've had a few customers looking for an Aruba response. There has been a lot of discussion the past few days about a new way to attack WPA2-PSK networks.

I will copy here the same thing that I posted on an internal message board: