On Thu, 2018-01-04 at 14:59 -0600, Denis Kenzior wrote: > So this implies userspace must pre-register for authentication > management frames, correct? And other applications could register to > receive these frames as well? Would it not be easier (and more secure) > to simply forward these directly to the application that triggered > CMD_CONNECT instead?
Only one will be able to register, so I think it's OK. We could even check that it's registered already at CONNECT time, I guess. > > + genlmsg_multicast_netns(&nl80211_fam, wiphy_net(&rdev->wiphy), msg, 0, > > + NL80211_MCGRP_MLME, gfp); > > Is there a reason this is being multicast and not unicast to the > application that triggered the CONNECT? Who else besides the supplicant > daemon might find this information useful? That's a good point, we should send this to the CONNECT owner (and thus obviously also require that there is one). johannes
