From: Jiri Benc <jbenc@suse.cz>
To: Michael Buesch <mb@bu3sch.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: d80211: current TKIP hwcrypto implementation seems to be broken
Date: Mon, 5 Feb 2007 21:43:33 +0100 [thread overview]
Message-ID: <20070205214333.4e77948e@griffin.suse.cz> (raw)
In-Reply-To: <200702041344.19117.mb@bu3sch.de>
On Sun, 4 Feb 2007 13:44:18 +0100, Michael Buesch wrote:
> We need the phase1 for bcm43xx. We need to upload it to
> card memory and we need to pass it on every TX on the DMA.
>
> So, currently we receive the phase1 key on the first
> encrypted TX. That's too late, as we already receive encrypted
> packets before that. bcm43xx needs the phase1 key (and the iv32)
> on RX. It uses the one uploaded into the card memory. But it
> is not uploaded, yet, as we did not TX any encrypted packet.
>
> I'd say the only solution to this is to implement the earlier
> suggested way of having a library function call to generate
> the keys. Of course, that needs some bookkeeping about the IVs
> and stuff.
> That library function would be called by bcm43xx before any
> traffic to get an initial phase1 key (and iv32) uploaded.
What if the key is changed by the user space? You won't know that and
won't call the library function then. I think it needs to be designed
in the opposite way - the stack will call a driver's callback.
Or am I missing something?
Jiri
--
Jiri Benc
SUSE Labs
next prev parent reply other threads:[~2007-02-05 20:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-04 12:44 d80211: current TKIP hwcrypto implementation seems to be broken Michael Buesch
2007-02-05 20:43 ` Jiri Benc [this message]
2007-02-05 21:38 ` Johannes Berg
2007-02-05 21:45 ` Johannes Berg
2007-02-05 21:48 ` Johannes Berg
2007-02-06 14:55 ` Michael Buesch
2007-02-12 18:30 ` Jouni Malinen
2007-02-12 21:39 ` Michael Buesch
2007-02-12 23:15 ` Tomas Winkler
2007-02-12 23:23 ` Michael Buesch
2007-02-12 23:54 ` Tomas Winkler
2007-02-13 0:10 ` Michael Buesch
2007-02-13 0:19 ` Tomas Winkler
2007-02-13 0:28 ` Jouni Malinen
2007-02-13 1:08 ` Tomas Winkler
2007-02-13 1:20 ` Jouni Malinen
2007-02-15 16:58 ` Tomas Winkler
2007-02-13 0:33 ` Michael Buesch
2007-02-13 1:09 ` Tomas Winkler
2007-02-12 23:53 ` Jouni Malinen
2007-02-13 0:06 ` Michael Buesch
2007-02-13 0:16 ` Michael Buesch
2007-02-13 16:18 ` Johannes Berg
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=20070205214333.4e77948e@griffin.suse.cz \
--to=jbenc@suse.cz \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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).