Hi Johannes,
On 12/05/2016 07:51 AM, Johannes Berg wrote:
On Fri, 2016-12-02 at 21:56 +0100, Andrew Zaborowski wrote:
Disconnect or deauthenticate when the owning socket is closed if this
flag has been supplied to CMD_CONNECT, CMD_AUTHENTICATE or
CMD_ASSOCIATE.
Huh. That I think needs a lot more commit log to justify this code -
why do you think this would be useful? Connection managers dying don't
really mean you need to disconnect immediately, after all, and if they
restart it's pretty simple to detect the existing connection and
perhaps even use it...
Detecting it is easy, sure. But I'm a bit lost on how you propose to
'use' it. The connection is active up until the next rekey event. If
rekey offloading is supported, then this might never involve user space.
But if it isn't (and I can't get rekey offload to work on any recent
kernel I tried) then how do you propose userspace obtains the rekey
counter, or the various keys used in the connection?
What about all the other state information? FT, Pre-Authentication, etc?
Can you point me to a connection manager that actually performs this
'reuse' and not just simply wipes the state clean when starting?
Regards,
-Denis
