Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: add APIs to allow keeping connections after WoWLAN
Date: Fri, 16 Aug 2013 12:58:34 +0200	[thread overview]
Message-ID: <1376650714.15299.17.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1376309240-2485-1-git-send-email-johannes@sipsolutions.net> (sfid-20130812_140728_802101_934A3D7D)

On Mon, 2013-08-12 at 14:07 +0200, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
> 
> In order to be able to (securely) keep connections alive after
> the system was suspended for WoWLAN, we need some additional
> APIs. We already have API (ieee80211_gtk_rekey_notify) to tell
> wpa_supplicant about the new replay counter if GTK rekeying
> was done by the device while the host was asleep, but that's
> not sufficient.
> 
> If GTK rekeying wasn't done, we need to tell the host about
> sequence counters for the GTK (and PTK regardless of rekeying)
> that was used while asleep, add ieee80211_set_key_rx_seq() for
> that.
> 
> If GTK rekeying was done, then we need to be able to disable
> the old keys (with ieee80211_remove_key()) and allocate the
> new GTK key(s) in mac80211 (with ieee80211_gtk_rekey_add()).
> 
> If protocol offload (e.g. ARP) is implemented, then also the
> TX sequence counter for the PTK must be updated, using the new
> ieee80211_set_key_tx_seq() function.

Applied.

johannes


      reply	other threads:[~2013-08-16 10:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12 12:07 [PATCH] mac80211: add APIs to allow keeping connections after WoWLAN Johannes Berg
2013-08-16 10:58 ` Johannes Berg [this message]

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=1376650714.15299.17.camel@jlt4.sipsolutions.net \
    --to=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