On Fri, 2017-12-29 at 12:29 -0600, Denis Kenzior wrote: > Agreed, requiring both attributes is less than ideal, but I tried to > make the initial RFC as minimal as possible. It also helped that iwd > uses SOCKET_OWNER by default. What can be done is to always set > conn_owner_nlportid and introduce another flag that would indicate > whether 'connection tear-down on application exit' was requested. > > However, my opinion is that the current SOCKET_OWNER behavior should > just be made default, especially for control port over nl80211 > connections, even if SOCKET_OWNER was not requested. Once the > controlling application dies, there's no hope of salvaging the > connection, perform rekeys, etc.
I think we should keep both attributes; it's better to be explicit that both are needed than to set socket-owner automatically. > The biggest issue was that each driver defines a set of management > frames it can accept via this mechanism. I'm not sure this is "the biggest issue", but I tend to agree with keeping them separate. johannes
