Open GoogleCodeExporter opened 8 years ago
For me worked right Ctrl + C
Original comment by ondrej.platek@gmail.com
on 18 Jun 2011 at 4:30
It kill wifite, it doesn't work at all
Under Ubuntu Natty
This is an huge issue
Original comment by Shiden...@gmail.com
on 10 Aug 2011 at 2:51
I'll download a version of 11.04 Natty and see if I can reproduce.
Original comment by der...@gmail.com
on 14 Aug 2011 at 5:48
[deleted comment]
[deleted comment]
[deleted comment]
I made a capture...
It appears that it happens randomly, but only one try of 4 will succeed to do
it.
Original comment by Shiden...@gmail.com
on 22 Aug 2011 at 1:25
Attachments:
Same here. Ctrl+C often kills wifite.
You could map "Stop scanning" to some less letal shortcut :)
Original comment by imorgi...@gmail.com
on 20 Jul 2012 at 8:37
[deleted comment]
Same here, first in Meego (v68) and now in Ubuntu (v68 & 85), Ctrl+C most times
kills wifite itself instead of stop scanning/cracking
Original comment by ekz...@gmail.com
on 16 Sep 2012 at 3:16
Agreed. Need to map this to something else. Some keyboards are really quick on
the rekey event.
Original comment by sethleedy
on 21 Apr 2013 at 9:21
I see in main page
"stop any attack with Ctrl+C, with options to continue, move onto next target,
skip to cracking, or exit" but what is the command to continue attack AP?
I boot backtrack5 R3 on USB boot, how to resume attack (use wifite.py) with
session file in reaver (i copy and save this file) when i reboot backtrack .
Original comment by sanglxa...@gmail.com
on 23 Sep 2013 at 1:45
This happens often to me as well.
It seems random. I even try to do it as quickly as possible and it still may
happen.
If some sort of alternate could be made, that would be great.
Original comment by sethleedy
on 17 Oct 2013 at 5:52
here too on ubuntu 12.04, i need to be very quick to not shut wifite down, but
isn't this a function in airodump-ng?
maybe make the ctrl+C less sensitive to shut it down, or use another shortcut?
Original comment by bva.mob...@gmail.com
on 10 Mar 2014 at 7:22
Original issue reported on code.google.com by
bum...@googlemail.com
on 31 May 2011 at 11:24