ndiswrapper + wpa_supplicant
Thu Dec 6 09:18:15 PST 2007
On Thu, 2007-12-06 at 11:50 -0500, Bryan Kadzban wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
> George N. White III wrote:
> > At present, some people are finding that NM unexpectedly connects to
> > an open AP, e.g., after the connection to a secure AP was dropped,
> Well, that sounds like a bug that should be fixed -- but I'm not sure
> that a simple change to avoid combining BSSes would be sufficient to
> prevent connection to rogue APs. I think that preventing this is a good
> idea, of course, but I'm not sure that showing the user the BSSID is
> going to do that.
It will only connect to that AP if you've connected to that SSID before.
In 0.7, it won't connect to that AP if you've told it to lock to a
specific BSSID too.
If NM connects to that SSID, you have at some point explicitly told NM
to do so.
> (Of course I don't know the nature of this sounds-like-a-bug behavior,
> either, so I may be way off base there too.)
> Anyway, carry on. It sounds like Dan understands what's really needed
> (from the crypto side anyway) to prevent this, so that's fine. I'm just
> being paranoid. ;-)
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> -----END PGP SIGNATURE-----
More information about the Hostap