From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <jkm@devicescape.com>
Cc: Hong Liu <hong.liu@intel.com>, Jiri Benc <jbenc@suse.cz>,
netdev <netdev@vger.kernel.org>
Subject: Re: about 802.11i IBSS support
Date: Wed, 25 Oct 2006 23:46:20 +0200 [thread overview]
Message-ID: <1161812780.8884.3.camel@johannes.berg> (raw)
In-Reply-To: <20061025154815.GA15348@instant802.com>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
On Wed, 2006-10-25 at 08:48 -0700, Jouni Malinen wrote:
> > 1. for the d80211 part: I don't think there will be much efforts.
> > We may add a group key to each sta_info for decrypting multicast data from that STA.
> > And in RX path, we need to add code to select the correct group key for decryption.
> > And also we need to store our own group key used to send multicast data to others.
>
> This will also include looking into how different WLAN chipsets
> have implemented (or will implement) hardware acceleration for such a
> case.
For bcm43xx, you can use any key for TX. At RX, the mac address of the
sender is used to look up which key to use (broadly spoken). But if the
frame is multicast, bcm43xx can only use the 4 default keys if enabled.
That said, we're recently started to reverse engineer the firmware and I
can see that it should be trivial to also do a mac address matching for
multicast frames and use different keys then.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2006-10-25 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 8:54 about 802.11i IBSS support Hong Liu
2006-10-25 13:05 ` Michael Buesch
2006-10-25 15:48 ` Jouni Malinen
2006-10-25 19:59 ` Simon Barber
2006-10-25 21:46 ` Johannes Berg [this message]
2006-10-26 2:47 ` Hong Liu
2006-10-26 3:26 ` Simon Barber
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=1161812780.8884.3.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=hong.liu@intel.com \
--cc=jbenc@suse.cz \
--cc=jkm@devicescape.com \
--cc=netdev@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).