On Thu, 2009-07-09 at 19:48 +0200, Johannes Berg wrote: > On Thu, 2009-07-09 at 13:13 -0400, Pavel Roskin wrote: > > > I think using random data is a problem by itself. Are we exposing > > random pieces of kernel memory in probe requests? That's bad. > > You misunderstood. wpa_supplicant _explicitly_ tells us it _wants_ to > use that 32-byte random SSID. It's just like it telling us it wants to > use the ssid "foobar" or "Pavel's House" or ... I don't see what we can > do, other than actually take it seriously and at least attempt to > connect to that network. That was the idea, expect that this random BSSID/SSID combo will simply fail to be found in a scan, and either the card driver will just keep periodically scanning to find the AP until another request comes in, or they will eventually just give up and idle. What it was meant to do was to stop the card from trying to keep re-associating to a previous AP now that the supplicant has terminated. See my just-posted mail a bit up in this thread as to why. WEXT sucks. Dan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
