Re: dwepcrack

Alan,

I have had a similar experience.  It has been awhile so I do not 
remember the specifics but this sounds like the same behavior that I 
had.  Just keep at it, different cards can take awhile.

David

Alan B. Clegg wrote:
> Unless the network is lying to me again, h1kari said: 
> 
> 
>>                      If you aren't collecting enough weak ivs, I'm guessing
>>that one of your wireless cards is running a driver that blocks out some of
>>the weak ivs or does the funky iv repeating stuff. If you're still having
>>problems, post more info to the list so we can try and figure out what's
>>going on.
> 
> 
> I've collected bits with:
> 
> --SNIP--
> #!/bin/sh
> wicontrol wi0 -p 3
> wicontrol wi0 -f 11
> prism2ctl wi0 -m
> dwepdump -w wi0 OUTPUT
> --SNIP--
> 
> followed by:
> 
> skippy 62} dwepcrack -w OUTPUT
> * dwepcrack v0.4 by h1kari <[email protected]> *
> * Copyright (c) Dachb0den Labs 2002 [http://dachb0den.com] *
> 
> reading in captured ivs, snap headers, and samples... 
> [... four hour delay ...]
> done
> total packets: 946146
> 
> calculating ksa probabilities...
>  0: 0/768 keys (!)
>  1: 51768/131328 keys (!)
>  2: 86812/197376 keys (!)
>  3: 86672/197120 keys (!)
>  4: 156924/328703 keys (!)
> 
> (!) insufficient ivs, must have > 60 for each key (!)
> (!) probability of success for each key with (!) < 0.5 (!)
> 
> warming up the grinder...
>  packet length: 44
>  init vector: 35:cc:3a
>  default tx key: 0
> 
> progress: 
> skippy 63} 
> 
> Note that this is between a Linksys AP (befw11s) running the most
> current firmware and an older Orinoco Gold card.
> 
> Any idea if the 4 hour (yes, 4 hour) delay is normal?  Once it hits the
> "Warming up the grinder" it only takes about 15 seconds to finish...
> 
> Is this functioning normally?
> 
> AlanC