Added beacon packet to handshake cap file for PMKID assoc attack #603
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello
Regarding #592
I was also having a problem completing this example
https://www.evilsocket.net/2019/02/13/Pwning-WiFi-networks-with-bettercap-and-the-PMKID-client-less-attack/
where there was no output file created from
hcxpcaptool -k pmkid.16800
It seems the beacon packet was missing from the handshake file.
This merge request adds the packet to the handshake file.
I have tested it locally and the hcxpcaptool now writes the hash to the file once the beacon packet is included
What an awesome project !! Thank you for it.