All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Jiri Benc <jbenc@suse.cz>
Cc: linux-wireless@vger.kernel.org
Subject: d80211: current TKIP hwcrypto implementation seems to be broken
Date: Sun, 4 Feb 2007 13:44:18 +0100	[thread overview]
Message-ID: <200702041344.19117.mb@bu3sch.de> (raw)

Current TKIP hwcrypto phase1+2 key support in d80211
seems to be broken. (At least for bcm43xx).

Let me explain what happens:
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.

I currently don't really know how to implement this. Any suggestion?

As a sideeffect, it would shrink the txcontrol by 16 bytes, again.

-- 
Greetings Michael.

             reply	other threads:[~2007-02-04 12:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-04 12:44 Michael Buesch [this message]
2007-02-05 20:43 ` d80211: current TKIP hwcrypto implementation seems to be broken Jiri Benc
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=200702041344.19117.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=jbenc@suse.cz \
    --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.