12-06-2017, 06:16 PM
12-06-2017, 06:27 PM
I only know of C implementations
12-06-2017, 06:29 PM
i did one for hccap before but its alot of time.
so i asked if someone already did it.
thanks anyway
so i asked if someone already did it.
thanks anyway
12-06-2017, 07:43 PM
If you already have one for hccap it should be easy to adopt to hccapx.
12-07-2017, 02:14 AM
not really easy but i should do it
12-07-2017, 10:26 AM
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
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
12-11-2017, 10:32 PM
first of all thanks all.
i make a class of handshake in java and convert cap to List<handshake>
handshake:
private String essid;
private String bssid;
private String station;
private String snonce;
private String anonce;
private String eapol;
private String eapolSize;
private String keyVersion;
private String keyMic;
i make a class of handshake in java and convert cap to List<handshake>
handshake:
private String essid;
private String bssid;
private String station;
private String snonce;
private String anonce;
private String eapol;
private String eapolSize;
private String keyVersion;
private String keyMic;