12-19-2020, 12:47 AM
(This post was last modified: 12-19-2020, 12:51 AM by crappy.follower.)
Hey,
Really enjoyed this tool and your work.
I have gone through the entire process of using hcxdumptools to capture wifi network data.
I have converted the captured data using hcxpcapngtool.
I then use hashcat mode 22000 to start a dictionary attack.
I need to take a step back and ensure I have collected the appropriate data.
I was wondering if there were any obvious ways to tell whether or not the captured data can be cracked? My concern is I have captured "synthetic hashes" (I read a post about this) which aren't actually capable of being cracked. For example, I have collected WPA 01 and WPA 02 data which has unknown MAC AP and Client data (hcxhashtool -i example.22000 --info=stdout).
When I enter the data into Hashcat, it starts the process, but not sure if its just making a bunch of sound and heat.
Is $ hcxhashtool -i example.22000 --info=stdout the indicator as to what hashes can be cracked? Despite many lines not having Mac AP and Client data?
Really enjoyed this tool and your work.
I have gone through the entire process of using hcxdumptools to capture wifi network data.
I have converted the captured data using hcxpcapngtool.
I then use hashcat mode 22000 to start a dictionary attack.
I need to take a step back and ensure I have collected the appropriate data.
I was wondering if there were any obvious ways to tell whether or not the captured data can be cracked? My concern is I have captured "synthetic hashes" (I read a post about this) which aren't actually capable of being cracked. For example, I have collected WPA 01 and WPA 02 data which has unknown MAC AP and Client data (hcxhashtool -i example.22000 --info=stdout).
When I enter the data into Hashcat, it starts the process, but not sure if its just making a bunch of sound and heat.
Is $ hcxhashtool -i example.22000 --info=stdout the indicator as to what hashes can be cracked? Despite many lines not having Mac AP and Client data?