From owner-freebsd-hardware Mon Oct 9 12:40: 9 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from alpo.whistle.com (s206m1.whistle.com [207.76.206.1]) by hub.freebsd.org (Postfix) with ESMTP id EF93C37B66D; Mon, 9 Oct 2000 12:40:04 -0700 (PDT) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id MAA54330; Mon, 9 Oct 2000 12:30:49 -0700 (PDT) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id MAA33408; Mon, 9 Oct 2000 12:30:19 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200010091930.MAA33408@whistle.com> Subject: Re: WEP keys for an driver In-Reply-To: <20001009115847.A2570@Odin.AC.HMC.Edu> from Brooks Davis at "Oct 9, 2000 11:58:47 am" To: Brooks Davis Date: Mon, 9 Oct 2000 12:30:19 -0700 (PDT) Cc: Dave Cornejo , Doug Ambrisko , freebsd-hardware@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brooks Davis writes: | On Mon, Oct 09, 2000 at 11:42:32AM -0700, Dave Cornejo wrote: | > Some comments on your code: | > - WEP keysare variable length from 5-13 bytes, you should just check for | > >=5 & <=13 (it seems odd, but I have seen networks that use the odd | > sizes). | | Since all the windows drivers I've looked at only allow 0, 5, and 13 | byte keys, I'd suggest only allowing those values. That's what | wicontrol does. That's what I recall from Windows and I allow 0, 5 or 13 characters as 0 -> erase key 0xDDDDDDDDDD -> set 40 bit 0xDDDDDDDDDDDDDDDDDDDDDDDDDD -> set 128 bit I also verified it did the right thing by booting back into Windows and then running the WEP utility to see if it made the right change. Also did it as hex since that is what the WEP utility did. The code would probably work with ASCII strings but how do you encode 0-255 as a character in an ASCII string? BTW my test string was 0x001122334455 (for 40 bit). Originally I wasn't doing a 40 bit or 128 and things didn't work. Once I started doing 40 bit or 128 bit keys then things worked fine. Since the programming doc didn't say anything about that I burned a few days on that :-( | > I didn't provide patches to ancontrol as you did, but I find ancontrol | > is getting way too nasty with its switches. Your patches look fine | > to me except that I'd really like to see a better way to specify | > volatile vs. persistent keys. | | You need to add ancontrol support or the patch is basicaly useless. I'm | looking forward to some sort of working crypto support for the aironet | cards. Well if you just download mine for now again at www.ambrisko.com/doug/an.patch.wep That will get you going. Some people other then myself are using it with success. It looks like it will get some more features since it looks like he has gleaned some more knowledge then I was told. Give it a try and let me know if you run into a problem. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message