On Tue, Dec 20, 2016 at 11:22:42AM +0000, Blanquicet-Melendez Jose (MM) wrote: > Ok, I understood that particular case but if I keep the network profiles always empty (i.e. Always remove them after disconnecting) and I keep track of WPS status using WPS.Event signal, I think there is no way that the network which wpa_supplicant connects to after "success" in WPS.Event is not the one I just received the credentials. Do you agree? Of course, if in the meanwhile there is an attempt from user to connect to another network (Create new network profile and select it), the WPS status must be clean. You may receive multiple credentials from a single WPS provisioning step, but if you do indeed remove all network profiles before starting the WPS provisioning step, the only available profiles for connection after that WPS step would indeed be the ones received from that instance of going through the WPS protocol. > On most of test we have done so far, at the end of the WPS operations there is only one network profile created. Although it's true that during the process one more network profile is created but it is automatically deleted by wpa_supplicant itself. So I just would have to remember that one, which is the same I will receive in Interface.PropertyChanged as "CurrentNetwork". Do you also agree here? No. While most use cases of WPS are probably provisioning a single credential, the WPS protocol itself has support for arbitrary number of credentials and as such, you may get multiple network profiles added from a single provisioning step. As such, the current network after successful connection is not necessarily the only network profile that was added. That's why I pointed at tracking the signals indicating when a new network profile is added during the WPS operation; there may be more than one of those signals. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
