-
I'm running Ubuntu Gutsy Gibbon, and tried to install wepattack, but I recieve the following error codes:
[code]
$ sudo make
gcc -fno-for-scope -c -D__LINUX_WLAN__ -D__I386__ -o wepattack.o wepattack.c
cc1: warning: command line option "-fno-for-scope" is valid for C++/ObjC++ but not for C
wepattack.c:30:18: error: zlib.h: No such file or directory
wepattack.c: In function...
2008-01-28 20:14:35 UTC by aorthr33
-
This is because a new behaviour of make 3.81.
It should probably be fixed in the Makefile.
2007-04-09 13:20:40 UTC by nobody
-
In function verify_crc32(), in file verify.c, the
variable "crc" suffers from endian issues. This
prevents wepattack to work sucessfuly on bid-endian
processors.
Here is a proposed solution:
#define SWAP32(x) \
x = ((((x) & 0x00ff0000) >> 8) | \
(((x) & 0x0000ff00) > 24) | \
(((x) & 0x000000ff)
2006-11-11 02:49:47 UTC by latinsud
-
Coffee to the rescue...
In src/Makefile on line 24 change
$(LD) $(LDFLAGS) -o $@ wepattack.o rc4.o wepfilter.o log.o\
to
$(LD) $(LDFLAGS) -o $@ wepattack.o rc4.o wepfilter.o log.o \
...it needs the space before the newline, at least on gcc 4.0.3.
2006-06-10 13:38:45 UTC by planalpha
-
I'm trying to compile 0.1.3 on umbuntu dapper. I get the following error:
gcc -o wepattack wepattack.o rc4.o wepfilter.o log.o\
modes.o misc.o verify.o keygen.o -lpcap -lz -lcrypto
gcc: log.omodes.o: No such file or directory
make: *** [wepattack] Error 1
Any ideas why? Google shows nothing...
Thanks.
2006-06-09 23:26:40 UTC by planalpha
-
There is a line in the make file that ends with log.o\
This causes gcc to fail while looking for log.omode.o
I removed the \ and moved the following line up and it
fixed the problem.
2006-05-28 02:28:20 UTC by nobody
-
Has anyone tried this and gotten it to work?
I consistently get the following error message:
Unknown option: "-wordfile:/home/john-1.6/run/wordlist"
when I run john by hand, I noted that it's options are looking for --, rather than just -, but when I changed it, I get the same problem.
If anyone has any ideas, I'd really appreciate hearing them.
Thanks
Bob.
2004-08-13 13:33:03 UTC by tyggerbob
-
yes, thats exactly how it works.
24 bit (IV) + 40 bit (key) = 64 bit security
24 bit (IV) + 104 bit (key= = 128 bis security.
2003-07-05 09:22:19 UTC by girardet
-
Is anybody aware of a good wep key dictionary. I would expect that a majority of APs have keys like 00000 or 0000000000000 or 01234 and other things like that. There are also a good many words that are the right length. The entire keyspace is probably too large to effectively test but all alphanumeric wouldn't be too unreasonable, certainly repetative or incrimenting keys would be doable.
2003-07-01 14:23:48 UTC by jerryshenk
-
HI! I read some paper about the wep attack but i still have some problem , as we know the share key was 24 bits IV and compose with 40bits we chose the key, The dictionary attack is the method to guess the key 40 bits we chose or not and my concept is wright or not ? any document can give me the detail about the attack about the dictionary method.thanks.
2003-04-06 16:38:24 UTC by billlee
