Date: Tue, 23 Mar 2004 23:05:11 -0500 From: Gary Corcoran <garycor@comcast.net> To: Sam Leffler <sam@errno.com> Cc: freebsd-mobile@freebsd.org Subject: Re: WEP problems with ndis and ath drivers Message-ID: <406108F7.3030704@comcast.net> In-Reply-To: <B0667184-7CD1-11D8-AA7B-000A95AD0668@errno.com> References: <20040321013533.GA37342@panzer.kdm.org> <B0667184-7CD1-11D8-AA7B-000A95AD0668@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sam Leffler wrote: > It appears your AP requires shared-key authentication to associate when > WEP is enabled. The current code in the tree does not support > shared-key authentication (it's actually a bad idea security-wise). I don't claim to be an "expert" on WiFi, but the project I'm on at work involves WiFi, so I've had to learn a few things. One thing I learned is that you have a choice of "open" or "shared-key" authentication, and I eventually found out what "open" means. It is supposedly better described as "no authentication", because your access point is "open", or usable without authentication. This is independent (on at least some access points) of whether you have WEP turned on. That is, with WEP on, you can have either open or shared-key authentication. On other acess points, however, it appears that if you have WEP turned on, then it implies shared-key, rather than the no-authentication "open" mode, which seems to make sense - if you want security, you don't want just anyone "authenticating". Hence I'm curious why, if "open" equates to "no" authentication, you suggest that shared-key authentication is a worse option? Perhaps it is - I'm just trying to learn a bit more... BTW, although I've only played with it a bit on FreeBSD and Linux, thanks for your work on the Atheros drivers, Sam. Gary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?406108F7.3030704>