Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Airodump has stopped" after pressing ctrl+c at list of targets #123

Closed
Kasperait opened this issue Aug 15, 2018 · 4 comments
Closed

"Airodump has stopped" after pressing ctrl+c at list of targets #123

Kasperait opened this issue Aug 15, 2018 · 4 comments

Comments

@Kasperait
Copy link

I downloaded wifite, from gihub. Started it all as usual, and here I choose the network to attack, but when I press ctr+c. I have goes such a mistake which I him correct.
Here is a video: https://youtu.be/Sg-k7oec9z8

@derv82
Copy link
Owner

derv82 commented Aug 16, 2018

This should be fixed in the latest version (2.1.7). Try it out (git pull or git clone) let me know if you still get this error.

@derv82 derv82 changed the title I have goes such a mistake which I him correct. "Airodump has stopped" after pressing ctrl+c at list of targets Aug 16, 2018
@kocheko
Copy link

kocheko commented Aug 25, 2018

its done, thanks a lot, work like a charm with both the wireless pci and the usb antenna, .. i suggest u guys may add some information how to fix this issue, as "updating the software" is not enough information for newbies( i didnt knew how to update only wifite , i ran git clone https://github.com/derv82/wifite.git but didnt update ) so i ran apt update && apt dist-upgrade
..thats saves any further questions imho

wifite 2.2.2
kali linux 2018.2

@Kasperait
Copy link
Author

Thank you very much. I did :git https://github.com/derv82/wifite.git And the error disappeared

@RaduNico
Copy link

I've run into similar issues, when pressing Ctrl+c during target scanning airmon-ng would crash. This is not such a big issue as Wifite did not crash and once airmon would crash the attacking phase wold start, however the except from the Scanner.init method would not properly catch the KeyboardInterrupt.

The issue seems to come from a too broad exception clause in Tshark->check_for_wps_and_update_targets, called by the Airodump.get_targets. There currently seem to be 4 except: lines of code that do accept any exception, including KeyboardInterrupt.

RaduNico added a commit to RaduNico/wifite2 that referenced this issue Nov 21, 2018
The issue was that sending Ctrl+C would not be caught by the
try-except clause inside the scanner if the keyboard interrupt
was sent while inside inner try-except blocks. This would
result in airodump crashing and the Scanner.find_targets()
function returning, instead of prompting the user with the
choice to stop the attack.
This could be the possible cause for issue derv82#123

TODO: catch specific exceptions where possible

Signed-off-by: Radu Nicolau <radunicolau102@gmail.com>
RaduNico added a commit to RaduNico/wifite2 that referenced this issue Feb 26, 2019
The issue was that sending Ctrl+C would not be caught by the
try-except clause inside the scanner if the keyboard interrupt
was sent while inside inner try-except blocks. This would
result in airodump crashing and the Scanner.find_targets()
function returning, instead of prompting the user with the
choice to stop the attack.
This could be the possible cause for issue derv82#123

TODO: catch specific exceptions where possible

Signed-off-by: Radu Nicolau <radunicolau102@gmail.com>
RaduNico added a commit to RaduNico/wifite2 that referenced this issue May 23, 2019
The issue was that sending Ctrl+C would not be caught by the
try-except clause inside the scanner if the keyboard interrupt
was sent while inside inner try-except blocks. This would
result in airodump crashing and the Scanner.find_targets()
function returning, instead of prompting the user with the
choice to stop the attack.
This could be the possible cause for issue derv82#123

TODO: catch specific exceptions where possible

Signed-off-by: Radu Nicolau <radunicolau102@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants