Hi, On Sun, 11 Oct 2020, at 19:14, Jouni Malinen wrote: > On Thu, Aug 20, 2020 at 01:46:57PM +0300, Dmitry Koroban wrote: > > Faced this issue on v2.6, but 2.10 seems to have it too. > > Steps to reproduce: > > 1. Start hostapd with WPS enabled > > 2. Change passphrase in hostapd.conf > > 3. Send SIGHUP to hostapd > > 4. Try to connect client using wps_pbc > > 5. Client receives old passphrase and cannot connect > There is a call to hostapd_update_wps() just before this context and > that function is the place to update whatever needs to be updated for > WPS. It would be cleaner to do this type of restarting of WPS there in > case WPS was started before reconfiguration instead of hardcoding > deinit/init to happen after that update function is executed. Has there been any follow-up on this, maybe an alternative implementation? I don’t see anything on the mailing list, but maybe I’m looking in a wrong place? -- Cheers, Andrej _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
