Re: General update

Miles,

On 8/28/02 7:28 PM, "Miles Nordin" <[email protected]> wrote:

>>>>>> "h" == h1kari  <[email protected]> writes:
> 
>    h> I'm planning on recoding dstumbler when I get some free
>    h> time to be totally monitor mode based and allow some nifty
>    h> features like: Single keystroke [...]
> 
> neat!
> 
> It would also be really cool if it:
> 
> * built and worked for the latest -stable and for -current on all
>  three BSDs

Agreed. The main reason why this hasn't been fully done yet is because I
have a limited set of hardware and time. If anyone is running netbsd or
freebsd and has some time to work on porting the openbsd-current patches
please be my guest. I mainly wrote these tools for my own convenience, and I
really only use them with openbsd-3.1 and -current and it requires a lot of
time that I don't have to blindly port patches for an OS that I'll probably
never use.

As far as I know and have seen, bsd-airtools-v0.2 runs on FreeBSD 4.4 and
4.6 and OpenBSD 3.1, bsd-airtools-current runs on OpenBSD-current. There
isn't any real NetBSD support yet, but with the new modifications to
-current it should make integration fairly easy.

> * could collect complete corruption-free packets useful for actually
>  cracking WEP, rather than merely serving as nonfunctional example
>  code.

I'm sorry, but if you consider dweputils a nonfunctional example of
wep-cracking code you might as well consider all wep cracking code out there
nonfunctional. I have yet to see airsnort or wepcrack.pl provide results
close to dweputils. I have also cracked numerous weped networks using that
code using the exact instructions included with the software, how many have
you tried to crack? Time and time again, I see people post questions
regarding not being able to crack wep and it's either related to:

1. not following the instructions
2. the ap or nodes are filtering weak ivs

If you can provide some specific examples of how the code is nonfunctional,
or any facts to back up your very elaborately illustrated argument for my
software being a "nonfunctional example", please be my guest.

> although admittedly these two features are probably not as fun to work
> on as the single-keystroke DoS kit, maybe now that your development
> branch is available from anoncvs other contributors will find it
> easier to polish up these rough edges.

If anyone wants to contribute working on support for the different OS's and
committing patches to the distributions, that would be great. I would love
to have the time to work on getting my software to run on every operating
system, work on updates every day, and help everyone get it running on their
system, but the bottom line is that I have to pay bills and eat and working
on bsd-airtools doesn't provide me with any of that.

I'm terribly sorry that I haven't been able to spend all of my sleeping and
waking hours working on making my code work for you. I know I should at
least provide you with that for all of the money that I charge for the
software.

Just my $0.03,
-h1kari

-- 
David Hulton <[email protected]>
Senior Researcher, Dachb0den Labs
http://www.dachb0den.com