hashcat Forum

So I've looked at some examples of other cracking WPA2 handshakes, which is why this boggles me.  Why am I getting what appears to be the shared hex key?  Shouldn't it be the plaintext key?  furthermore, if this really is the plaintext key, then I would have needed to set a rule to 36 characters (plus colons and SSID).  I only set 10 characters.  Anyways, here is my result.

ATT802:383bc8999eb2:5065f3fa89d1:8790560512

I know that the username/SSID is printed, which explains the "ATT802," but what is the rest?  Is that hex? If so, how do I get the ASCII key? I tried plugging that into a converter and just got gibberish.


This is my first attempt at this process so bear with me while I learn.  Thanks for the help.

So after researching, it seems like the point of the handshake cracking is to obtain the ASCII derivative of this key/SSID combo.
https://security.stackexchange.com/questi...y-and-ssid

Is this hex key an expected response from hashcat (cudahashcat)? I also used the --show argument to spit this result back out to validate the finding (thinking there might possibly be a mismatched output).

SSID: ATT802
AP MAC address: 383bc8999eb2
Client MAC address: 5065f3fa89d1
WPA-PSK: 8790560512

"I only set 10 characters" -> 8790560512 length 10.
What's the problem?

(02-14-2016, 03:15 PM)rico Wrote: [ -> ]SSID: ATT802
AP MAC address: 383bc8999eb2
Client MAC address: 5065f3fa89d1
WPA-PSK: 8790560512

"I only set 10 characters" -> 8790560512 length 10.
What's the problem?

I didn't realize hashcat spit it out in that format.  I was expecting just the passphrase but this format makes sense for a list of results to distinguish between them.  I couldn't find the proper format in any manual or wiki here so that's why I asked.  Thanks for the assist!

that could be the wifi password
If memory serves me correctly you need 8-63 characters for wpa
the standard us keyboard has 95 characters including the space.