Open frantisekz opened 12 years ago
I ran into this bug during development but I could not reproduce it consistently.
What operating system are you running? What version of python (python -V)?
I will let you know if I find a fix for this in the mean time.
Ubuntu 12.04 Beta (almost Beta 2 :D), x86_64, stock kernel with pacthes through DKMS (driver for cpu fan, etc.) Python 2.7.3rc2 And yes, this bug cannot be reproduced :(
You could change the shortcut to 'q' instead of CTRL+C even if you can't reproduce the bug (I think it will solve it). BTW great work on this.
Had the same problem here with CTRL+C on Ubuntu 12.04 beta2. But today with the latest updates it seems to be solved
I'll leave this issue open in case other people have similar problems.
Thanks everyone for having patience on this issue.
I have the same issue. Pretty annoying! I am using Ubuntu 12.04 LTS and Python 2.7.3. Can we not just change the key to say CTRL + R (ready) for example.
[+] scanning (mon0), updates at 5 sec intervals, CTRL+C when ready.
NUM ESSID CH ENCR POWER WPS? CLIENT
1 (00:1F:1F:xx:xx:xx) 158 WPA 99db no
2 xxxxx 11 WPA2 64db wps
3 xxxxxxxxxx 4 WPA2 52db no
4 xxxxxxxxx 11 WPA 38db no client
(^C) interrupted
[+] quitting
:(
+1, i have hotkey 'q'
I am currently working on a module that will replace the Try: Except KeyboardInterrupt: way of breaking a loop. Kind of busy so it might take a while.
Sounds good, but seriously, no rush.
Update: I found the source of the bug, it was me using gksudo to run a bash script on my desktop.
Running:
$ gksudo python wifite.py
crashes on Ctrl+C
while running:
$ sudo python wifite.py
does not crash on Ctrl+C.
Also, the porting in a new input method was really buggy, hoaky, and dumb. Abandoning the mod.
Hi guys, I'm having this issue right now. Whenever I press CTRL+C to stop scanning, wifite closes itself.
I tried running wifite with the following commands:
$ wifite
$ python wifite.py
$ python2.7 wifite.py
but nothing seems to work.
this is my output.
thor@Mjolnir:~/wifite$ sudo python2.7 wifite.py
.;' `;,
.;' ,;' `;, `;, WiFite v2 (r87)
.;' ,;' ,;' `;, `;, `;,
:: :: : ( ) : :: :: automated wireless auditor
':. ':. ':. /_\ ,:' ,:' ,:'
':. ':. /___\ ,:' ,:' designed for Linux
':. /_____\ ,:'
/ \
[+] scanning for wireless devices...
[+] available wireless devices:
1. wlan0 Atheros ath9k - [phy1]
2. wlan1 Atheros ath5k - [phy0]
[+] select number of device to put into monitor mode (1-2): 2
[+] enabling monitor mode on wlan1... done
[+] initializing scan (mon0), updates at 5 sec intervals, CTRL+C when ready.
[0:00:04] scanning wireless networks. 0 targets and 0 clients found
[+] scanning (mon0), updates at 5 sec intervals, CTRL+C when ready.
NUM ESSID CH ENCR POWER WPS? CLIENT
--- -------------------- -- ---- ----- ---- ------
1 ARRIS****** 1 WPA2 15db no
2 DIRECT***** 1 WPA2 13db no
3 D****C***** 1 WPA2 13db no
4 ARRIS-***** 1 WPA2 10db no
5 J.**********. 1 WPA 10db no client
6 D-Link_DIR-615 1 WPA2 9db no
7 Prue***** 1 WPA2 9db no
^C0:00:11] scanning wireless networks. 11 targets and 2 clients found
(^C) interrupted
[+] disabling monitor mode on mon0... done
[+] quitting
thor@Mjolnir:~/wifite$
I tried using wifite and wifite-ng by aanarchy, and it doesn't work properly either. Can you help me?
Thanks in advance.
Sometimes, when i Am at monitor mode and press ctrl+c, program will exit. But, it shouldn't . PRessing ctrl+c at monitor mode should end monitoring and offers next steps (sometimes, it do so).
LOG:
[+] scanning (mon0), updates at 5 sec intervals, CTRL+C when ready.
NUM ESSID CH ENCR POWER WPS? CLIENT
[0:00:23] scanning wireless networks. 2 targets and 6 clients found
(^C) interrupted <<<ctrl+c pressed
[+] disabling monitor mode on mon0... done [+] quitting fanys@fanys-netbook:~/temp/wifi/wifite$
And now correct behavior:
NUM ESSID CH ENCR POWER WPS? CLIENT
[+] select target numbers (1-2) separated by commas, or 'all':
Sorry for my bad English.