linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias May <matthias.may@neratec.com>
To: Johannes Berg <johannes@sipsolutions.net>,
	Emmanuel Grumbach <egrumbach@gmail.com>,
	voncken <cedric.voncken@acksys.fr>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Mac80211 : Wpa rekeying issue
Date: Tue, 5 Jan 2016 11:54:27 +0100	[thread overview]
Message-ID: <568BA0E3.5080905@neratec.com> (raw)
In-Reply-To: <1451987939.12357.18.camel@sipsolutions.net>

On 05/01/16 10:58, Johannes Berg wrote:
> On Tue, 2016-01-05 at 10:47 +0100, Matthias May wrote:
>
>>
>> We've encountered exactly this problem in a mix of devices where one
>> applies key material faster than the other. (ath9k and aquilla)
>> As a workaround we check on the STA if we are authorized when
>> updating/checking CCMP. (see attached patches)
>>
>
> Those don't really seem safe to use either.
>
> johannes
>

Not safe as in "access to stuff which has to be locked", or not safe as 
in "a CCMP replay attack is possible"?
When changing this we argumented that since we are not really connected 
yet, a CCMP replay attack doesn't really make sense.

Matthias

  reply	other threads:[~2016-01-05 10:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-29 13:01 Mac80211 : Wpa rekeying issue Cedric VONCKEN
2015-12-29 14:19 ` Emmanuel Grumbach
2015-12-29 15:23   ` voncken
2015-12-31  8:12     ` voncken
2015-12-31  8:41       ` Emmanuel Grumbach
2015-12-31 10:15         ` voncken
2015-12-31 15:25           ` Ben Greear
2016-01-05  9:19         ` Johannes Berg
2016-01-05  9:47         ` Matthias May
2016-01-05  9:58           ` Johannes Berg
2016-01-05 10:54             ` Matthias May [this message]
2016-01-05 15:50               ` Johannes Berg
2016-01-06  9:09                 ` Matthias May
2016-01-07 21:06                   ` Johannes Berg
2016-01-07 21:15         ` Johannes Berg
2016-01-12 11:38           ` Emmanuel Grumbach

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=568BA0E3.5080905@neratec.com \
    --to=matthias.may@neratec.com \
    --cc=cedric.voncken@acksys.fr \
    --cc=egrumbach@gmail.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).