Besside-ng: output "wpa.cap" includes only 1 handshake, rest of file is corrupt #2425
Replies: 2 comments 1 reply
-
Upon closer inspection with a hex editor, the wpa.cap file does NOT include the ASCII ESSIDs of any captured networks EXCEPT the 1st one. |
Beta Was this translation helpful? Give feedback.
-
Redo the transfer in binary mode. Fixing a PCAP is easy to do manually: open in Wireshark, mark first frame. Go to the end, mark second to last, then save the between these 2 marked frames. |
Beta Was this translation helpful? Give feedback.
-
Besside-ng UP to version 1.5.2 was working fine.
From that version on 2 bugs started to exist:
1)"bad beacon error" which was thankfully fixed in the latest current version
2) wpa.cap output files are corrupt. The file includes always just 1 valid WPA handshake and the rest of the file is corrupt.
If for example Besside-ng manages to capture 8 handshakes running "aircrack-ng wpa.cap" results to:
#1 BSSID ESSID WPA (1 handshake) <-- this 1st handshake is valid
and then this error is shown: "Invalid packet capture length 0 - corrupted file"?
Any ideas?
Beta Was this translation helpful? Give feedback.
All reactions