hostupd rc-script is scheduled for running in a trail of rc-scripts thus it should run as much close to netif as possible: if one is using wireless adapter in hostap mode, nnetif configures it into this mode BUT with no security applied. The interval between netif and hostapd launches this wireless network runs unsecured. Fix: 1) hostapd should be inserted into NETWORKING REQUIRE record. 2) netif should be inserted into hostapd REQUIRE record. This will significantly reduce period of unsecured wireless network running though not eliminating it totally. Another approach is to introduce hostapd_ifaces variable and controlling wireless interface UP/DOWN state from rc-script. Ideally both of approaches should be implemented. How-To-Repeat: Configure wlan0 into hostap mode, configure hostapd. Reboot machine and observe your wireless network running without any security for 30-40 seconds or even couple of minutes.
Responsible Changed From-To: freebsd-bugs->freebsd-wireless Over to maintainer(s).
batch change: For bugs that match the following - Status Is In progress AND - Untouched since 2018-01-01. AND - Affects Base System OR Documentation DO: Reset to open status. Note: I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Since base r296226 the interface is just created, but not started if wpa_supplicant / hostapd is used; both are capable to run the interface during startup.