From: Volker Braun <volker.braun@physik.hu-berlin.de>
To: Michael Wu <flamingice@sourmilk.net>
Cc: linux-wireless@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
Jiri Benc <jbenc@suse.cz>
Subject: Re: [PATCHv2] mac80211: dynamic wep
Date: Mon, 13 Aug 2007 11:12:50 -0400 [thread overview]
Message-ID: <1187017970.14416.23.camel@carrot.hep.upenn.edu> (raw)
In-Reply-To: <200708130054.57899.flamingice@sourmilk.net>
I completely missed that privacy==confidentiality and includes all
encryption schemes, thanks.
On Mon, 2007-08-13 at 00:54 -0700, Michael Wu wrote:
> > - if (keyidx >= 0 && keyidx < NUM_DEFAULT_KEYS &&
> > - (!rx->sta || !rx->sta->key || keyidx > 0))
> > - rx->key = rx->sdata->keys[keyidx];
> So it looks like the keyidx > 0 check here is the source of the RX problems. I
> think we can store the keyidx of the individual key to compare against
> instead of assuming all individual keys have a keyidx of 0.
Correct me if I'm wrong, but I'm reading the standard like this: For WEP
keys one can have up to 4 default keys (rx->sdata->keys[keyidx]), and a
varying number (but at least 10) per-STA keys (rx->sta->key). On
receiving a unicast packet, you use the per-STA key if available (and
discard keyidx). Only if there is no per-STA key, or the packet is
multicast, you use the keyidx-th default key.
So you cannot rely on keyidx and you must have a check for unicast vs.
multicast somewhere.
Volker
next prev parent reply other threads:[~2007-08-13 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 23:31 [PATCHv2] mac80211: dynamic wep Volker Braun
2007-08-13 7:54 ` Michael Wu
2007-08-13 8:54 ` Johannes Berg
2007-08-13 15:48 ` Michael Wu
2007-08-13 15:12 ` Volker Braun [this message]
2007-08-15 1:47 ` Johannes Berg
2007-08-15 15:51 ` Volker Braun
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=1187017970.14416.23.camel@carrot.hep.upenn.edu \
--to=volker.braun@physik.hu-berlin.de \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--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