|
f0urtyfive: perhaps the configure script haven't detected fine your xeon processor and you haven't compiled with the proper gcc optimizations. Check it. I tried to detect the gcc version and processor type in configure, and apply the best optimizations in each case.
firefighter99: not slow. The c/s in heuristic attack (FMS) has nothing to do with c/s in bruteforce mode.
All of you:
1) Please use --debug 1 --debugkey (put your key finishing in ':') . It will show you statistics about the number of weak keys per byte (of the real key branch). Paste here in the forum the lines that will appear. These lines tells you the number of weak packets and the candidate keys. If all went ok, you should see your real key bytes the first or second ones.
2) Sometimes the card adds an special 4 bytes tail. You should use --fcs to tell weplab about that. Otherwise weplab will take these 4 bytes as the packet's CRC instead of the real CRC, so the real WEP key will not test fine agains the packet. If you can see your real key bytes with --debugkey but still weplab doesnt find it, just try with --fcs
3) Please tell me which card do you have, which drivers, and what did you do to put it into monitor mode so weplab is able to capture packets. I'm doing the README and FAQ for next releases, and this information will be very helpfull for me.
Thank you very much for your tests.
|