New hccapx format explained

[TheFool]

[
Here are my results with "AP.cap":

Wireless Password Auditor (Elcomsoft) > Detects 2 handshakes:

1 (valid) = FAILED
2 (no data) = FAILED

Wireless Password Recovery (Passcape) > Detects 2 handshakes:

1 (invalid) = CRACKED
2 (unknown) = CRACKED

cap2hccapx converter > Detects 6 handshakes:
hashcat results:

1 (P0) = CRACKED
2 (P0) = CRACKED
3 (P0) = FAILED
4 (P0) = CRACKED
5 (P2) = FAILED
6 (P2) = CRACKED

In this experiment with AP.cap, I have also discovered something new & weird. When running an attack on a SINGLE .hccapx file with all 6 handshakes, the result is 3 out of 6 get cracked. However, when manually separating the 6 handshakes each into its own individual .hccapx file and attacking them one-by-one, *4* out of 6 get cracked.

Thanks for the info!

I am a newbie/fool so I don't understand everything you posted..  What I did was take the raw .cap file and run it through the cap2hccapx converter, then sent hashcat to work on it. (Which took 1 second, because of my single-word wordlist).  But.. no luck... "hashcat exhausted."

So.. it failed.

Then.. I took the same .cap file and converted it with aircrack-ng, and ran it through an older version of hashcat.. Boom, it cracked.

So how were you able to get 3/6 cracked on a single hccapx when I got no results at all? :/