Thanks for taking the time to make this, updating backtrack manually is a pain.
this is what I got after locate aircrack-ng:
/pentest/wireless/aircrack-ng
/usr/local/bin/aircrack-ng
/usr/local/share/man/man1/aircrack-ng.1
/usr/share/applications/backtrack-aircrack-ng.desktop
/var/lib/dpkg/info/aircrack-ng.changelog
/var/lib/dpkg/info/aircrack-ng.copyright
/var/lib/dpkg/info/aircrack-ng.list
/var/lib/dpkg/info/aircrack-ng.postinst
so this script updates backtrack itself or just the tools... and I thought (apt-get dist-upgrade / update) updates backtrack....
Wiffy-Auto-Cracker - was the best thing that ever happen to me. :) Wo0oT :)
AWUSO36H_500mW_5dBi Antenna
Unfortunately noone has been able to duplicate your problem. However, Gitsnik gave you some very helpful advice which you seem to have maybe overlooked. He told you to issue the command:
root@bt:~# which aircrack-ng
returning this result:
root@bt:~# /usr/local/bin/aircrack-ng
the command "which" does not just locate/find every instance of a file on a hdd; which (not the command which) can often return way more information than you need to be looking at.
DESCRIPTION
Which takes one or more arguments. For each of its arguments it prints to stdout the full path of the executables that would have been executed when this argument had been entered at the shell prompt. It does this by searching for an executable or script in the directories listed in the environment variable PATH using the same algorithm as bash(1).
it's definitely worth learning the "which" command's uses.
this is from a day or 2 old "fresh install" after using Sickness' python script to *update all* including the wireless toolset.
root@bt:~# clear
root@bt:~# cd /pentest/wireless/aircrack-ng/
root@bt:/pentest/wireless/aircrack-ng# dir
AUTHORS contrib lib Makefile patchchk scripts VERSION
ChangeLog evalrev LICENSE manpages patches src
common.mak INSTALLING LICENSE.OpenSSL packages README test
root@bt:/pentest/wireless/aircrack-ng# aircrack-ng
Aircrack-ng 1.1 r1904 - (C) 2006-2010 Thomas d'Otreppe
Original work: Christophe Devine
http://www.aircrack-ng.org
usage: aircrack-ng [options] <.cap / .ivs file(s)>
Common options:
-a <amode> : force attack mode (1/WEP, 2/WPA-PSK)
-e <essid> : target selection: network identifier
-b <bssid> : target selection: access point's MAC
-p <nbcpu> : # of CPU to use (default: all CPUs)
-q : enable quiet mode (no status output)
-C <macs> : merge the given APs to a virtual one
-l <file> : write key to file
Static WEP cracking options:
-c : search alpha-numeric characters only
-t : search binary coded decimal chr only
-h : search the numeric key for Fritz!BOX
-d <mask> : use masking of the key (A1:XX:CF:YY)
-m <maddr> : MAC address to filter usable packets
-n <nbits> : WEP key length : 64/128/152/256/512
-i <index> : WEP key index (1 to 4), default: any
-f <fudge> : bruteforce fudge factor, default: 2
-k <korek> : disable one attack method (1 to 17)
-x or -x0 : disable bruteforce for last keybytes
-x1 : last keybyte bruteforcing (default)
-x2 : enable last 2 keybytes bruteforcing
-X : disable bruteforce multithreading
-y : experimental single bruteforce mode
-K : use only old KoreK attacks (pre-PTW)
-s : show the key in ASCII while cracking
-M <num> : specify maximum number of IVs to use
-D : WEP decloak, skips broken keystreams
-P <num> : PTW debug: 1: disable Klein, 2: PTW
-1 : run only 1 try to crack key with PTW
WEP and WPA-PSK cracking options:
-w <words> : path to wordlist(s) filename(s)
WPA-PSK options:
-E <file> : create EWSA Project file v3
-S : WPA cracking speed test
-r <DB> : path to airolib-ng database
(Cannot be used with -w)
Other options:
-u : Displays # of CPUs & MMX/SSE support
--help : Displays this usage screen
No file to crack specified.
root@bt:/pentest/wireless/aircrack-ng# clear
i hate to be blunt or seemingly unhelpful; but you are either doing something wrong, or have broken something.
Last edited by clone; 08-17-2011 at 03:04 AM.