From: Denis Kenzior <denkenz@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Andrew Zaborowski <andrew.zaborowski@intel.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH][RFC] cfg80211: NL80211_ATTR_SOCKET_OWNER support for CMD_CONNECT
Date: Mon, 5 Dec 2016 09:05:47 -0600 [thread overview]
Message-ID: <5845824B.4090304@gmail.com> (raw)
In-Reply-To: <1480949899.31788.34.camel@sipsolutions.net>
Hi Johannes,
On 12/05/2016 08:58 AM, Johannes Berg wrote:
>
>> 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?
>
> Well, no, that'd only work with an open connection :)
>
And even that is questionable in my mind for some of the more advanced
cases.
But I'm not sure what your point is, do you still have objections to
this approach?
Regards,
-Denis
next prev parent reply other threads:[~2016-12-05 15:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 20:56 [PATCH][RFC] cfg80211: NL80211_ATTR_SOCKET_OWNER support for CMD_CONNECT Andrew Zaborowski
2016-12-05 13:51 ` Johannes Berg
2016-12-05 14:55 ` Denis Kenzior
2016-12-05 14:58 ` Johannes Berg
2016-12-05 15:05 ` Denis Kenzior [this message]
2016-12-05 15:14 ` Johannes Berg
2016-12-05 15:32 ` Denis Kenzior
2016-12-06 7:16 ` Johannes Berg
2016-12-06 21:42 ` Denis Kenzior
2016-12-07 1:40 ` Andrew Zaborowski
2016-12-07 6:19 ` Johannes Berg
2016-12-07 9:49 ` Andrew Zaborowski
2016-12-07 6:15 ` Johannes Berg
2016-12-07 6:40 ` Denis Kenzior
2016-12-07 6:48 ` Johannes Berg
2016-12-07 7:07 ` Denis Kenzior
2016-12-07 7:38 ` Johannes Berg
2016-12-05 15:40 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5845824B.4090304@gmail.com \
--to=denkenz@gmail.com \
--cc=andrew.zaborowski@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).