All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Does mac80211 guarantee no data frames are sent to driver until encryption is setup?
Date: Fri, 13 Nov 2015 13:55:00 -0800	[thread overview]
Message-ID: <56465C34.1090503@candelatech.com> (raw)
In-Reply-To: <CALhHN=qF55mHxqz6iX0PSHdBcMa_t6XYgXdkSt+Tt4W9gkFFYA@mail.gmail.com>

On 11/12/2015 10:14 PM, Janusz Dziedzic wrote:
> On 13 November 2015 at 01:59, Ben Greear <greearb@candelatech.com> wrote:
>> A certain firmware tries to do EAPOL inspection and only allow data pkts
>> to be sent after the 4-way M4 has been sent, for instance.
>>
>> This was breaking .11r because in that case you don't do the 4-way after
>> roaming, so the firmware was waiting forever for an M4 to be sent and
>> thus all tx data was hung.
>>
>> I managed to get this working by just removing all of the EAPOL inspection
>> from the firmware,
>> but I am thinking that if the stack will send data packets to the driver
>> before 4-way auth is completed and keys are set, then maybe I would
>> be opening up a race where un-encrypted frames could hit the air.
>>
>> Any idea what protections, if any, the mac80211 stack provides
>> for this case?
>>
> Check WLAN_STA_AUTHORIZED in mac80211.

Thanks for the hint.  Looks like my firmware change should
be perfectly safe in that case.

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


      reply	other threads:[~2015-11-13 21:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13  0:59 Does mac80211 guarantee no data frames are sent to driver until encryption is setup? Ben Greear
2015-11-13  6:14 ` Janusz Dziedzic
2015-11-13 21:55   ` Ben Greear [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=56465C34.1090503@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=janusz.dziedzic@tieto.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.