Fixes for WPA2 handshake capture and new version of tshark #77
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Encountered a bug caused by tshark because it now requires that the
-2switch is added when using-R. Added in-2everywhere that-Ris used with tshark. Chose this over-Ybecause in theory, it should be faster.Also was encountering an issue where wifite would not properly grab and process WPA2 handshakes. Turns out something was happening with the temporary pcaps that are being written, and they end up being corrupted. Implemented a fix for this that checks for and utilizes
pcapfix.pcapfixis included in both the Ubuntu and Kali repositories, so this shouldn't be an issue for most platforms.Thanks to @violentlydave for major assistance with this.