WLAN does not check BSSID (AP mac address)

Thanks for the answer. I can say that before Jolla I had used N900, N9 and Nexus 4 (besides Windows devices) and they did not operate in similar way. Each device checked the BSSID of the access point.

I still believe that free roaming between the networks is not worth of such security risk when I can connect to the open network or even to the "pinnaple" router

@jberezhnoy that is not how wlan works, that is not how networking works... bssids are used for identifying a specific hardware not a specific network (you'd need to permit 50+ APs on a campus to properly use the campus wlan) just like a mac identifies hardware and not a network. This is specifically crutial with 2+ APs, if a wlan device should bind to known bssids only that is becoming a specific enterprise grade setup not the other way round... there is only one case where it counts into, that is silent APs but that works a tad different than you might think...

@chemist thank you for your comment. In my original post i did not mention that my 'Home' access point is set up for wpa2 mode. Maybe the abscence of that fact caused some misunderstanding. The 802.1x standard describes how wpa/wpa2 authorization is designated to work. To keep it simple: the access points are identified by BSSID (mac address), not by network name (SSID). The preshared key is a kind of salted using the BSSID. I.e. if you have a wpa/wpa2 password hash for access point 1, it will not work with access point 2, unless both access points have the same BSSIDs and SSIDs. That is why the above scenario with 50APs is not relevant in our case. In such cases the 50APs work either in a repeater mode (i.e. they are not access points, but simple repeaters), or use different authentication mode (e.g. radius server). This is how wlan shall work according to the standards. Otherwise somebody can create an access point with SSID 'home' (or whichever else) and listen your traffic, while you will think you are connected to your home/campus network. I hope it is clear now that this bug is not related to seamless roaming between your home or campus wlans. As i understand current approach does not comply with authorization standard.

p.s. even bloody iphone does not behave in that way. tested on my sister's device (also tested thus evening on ubuntu, windows7 and android). sorry fir punctuation and mjstakes, typing from my Jolla

wpa-psk uses the ssid for salting... your turn! (same password hash works on a wpa-psk roaming network) - well never mind, it won't help your cause to understand how it works... you want your wlan not connect to BSSIDs you did not authenticate to previously by hand...

you are right that PMK is salted/hashed with ssid, while PTK does need BSSID of the AP. but the point is that device shall not try to send previously saved password to all networks with identical ssid, shall it? and ask for another password if the saved one did not match!g