[ask] cap to hccapx
#6
Hi ghsi10.
Nice idea (a python/java port).
But if you do that, please do not write this message_pairs into your converted hccapx:
MESSAGE_PAIR_M32E3 (3)
MESSAGE_PAIR_M32E3 (131)
MESSAGE_PAIR_M34E3 (4)
MESSAGE_PAIR_M34E3 (132)
It is not possible to convert them back to a cap.

Please use instead:
MESSAGE_PAIR_M32E2 (2)
MESSAGE_PAIR_M32E2 (130)
MESSAGE_PAIR_M34E4 (5)
MESSAGE_PAIR_M34E4 (133)
This message_pairs can be converted back to a cap.
Set also bit 8 in the message_pair value if you skip the replaycount check (we need this for nonce-error-corrections).
Add also detection of cleaned caps (timestamp = 0). We need the timestamp to calculate the EAPOL timer values.
Set bit 8 on cleaned caps or ignore that caps.

It's just in case that your python/java conversion program or the converted caps are published in www.
We are running into heavy issues using hccapx files from a conversion tool that doesn't take care about this.
If you need some informations about 802.11 frames, let me know.

The conversion is easy to do. The new struct can be found here: https://hashcat.net/wiki/doku.php?id=hccapx
Only a few additional fields must be added.

Cheers


Messages In This Thread
[ask] cap to hccapx - by ghsi10 - 12-06-2017, 06:16 PM
RE: [ask] cap to hccapx - by undeath - 12-06-2017, 06:27 PM
RE: [ask] cap to hccapx - by ghsi10 - 12-06-2017, 06:29 PM
RE: [ask] cap to hccapx - by undeath - 12-06-2017, 07:43 PM
RE: [ask] cap to hccapx - by ghsi10 - 12-07-2017, 02:14 AM
RE: [ask] cap to hccapx - by ZerBea - 12-07-2017, 10:26 AM
RE: [ask] cap to hccapx - by ghsi10 - 12-11-2017, 10:32 PM