From: Michael Buesch <mb@bu3sch.de>
To: "Jouni Malinen" <jkm@devicescape.com>
Cc: Jiri Benc <jbenc@suse.cz>, linux-wireless@vger.kernel.org
Subject: Re: d80211: current TKIP hwcrypto implementation seems to be broken
Date: Tue, 13 Feb 2007 01:06:37 +0100 [thread overview]
Message-ID: <200702130106.37999.mb@bu3sch.de> (raw)
In-Reply-To: <20070212235341.GD16597@instant802.com>
On Tuesday 13 February 2007 00:53, Jouni Malinen wrote:
> On Mon, Feb 12, 2007 at 10:39:31PM +0100, Michael Buesch wrote:
>
> > What happens on RX when the iv32 wraps. Well, it simply won't decrypt
> > the frame. What we must do then is upload a new key as fast as possible.
> > The undecrypted frame can be either decrypted in SW (which I think d80211
> > can do. At least with minor additional changes), or we drop it.
>
> That "iv32 wrap" should have been "iv32 changes" (phase1 key changes
Yep, I'm sorry. It should be iv32, of course.
> whenever iv16 changes, i.e., when iv32 is incremented by one). d80211
> does indeed support software decryption for this case, so it is fine to
> just pass the undecrypted frame up and marking it as such. This was
> needed for some of the TKIP cases with Atheros.
That's really cool.
--
Greetings Michael.
next prev parent reply other threads:[~2007-02-13 0:06 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
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 [this message]
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=200702130106.37999.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=jbenc@suse.cz \
--cc=jkm@devicescape.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 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).