From: Jouni Malinen <jkm@devicescape.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Michael Wu <flamingice@sourmilk.net>,
jbenc@suse.cz, linville@tuxdriver.com, netdev@vger.kernel.org,
jkmaline@cc.hut.fi
Subject: Re: michael_mic in crypto api?
Date: Wed, 19 Jul 2006 09:19:13 -0700 [thread overview]
Message-ID: <20060719161913.GA15317@instant802.com> (raw)
In-Reply-To: <E1G3E8f-0007xk-00@gondolin.me.apana.org.au>
On Thu, Jul 20, 2006 at 01:39:05AM +1000, Herbert Xu wrote:
> Michael Wu <flamingice@sourmilk.net> wrote:
> > Simplicity and consistency. Whereas the relatively simple mic part of the TKIP
> > algorithm is in crypto API, the (more important, more complicated) key mixing
> > part is not in crypto api.
> Sure, I don't mind either way. I think Jouni wrote this originally,
> maybe he can share his thoughts with us?
I was more or less told that TKIP implementation cannot be included in
the kernel tree before this was moved into crypto api.. I don't really
care much where it is, but since it is now in crypto api, it would sound
easiest to just keep it there. If someone really wants to move it away
from there and into TKIP code in ieee80211/d80211, feel free to do that.
However, at least for some time, there are two different TKIP
implementations (net/ieee80211 and net/d80211) so this would mean
duplicating Michael MIC implementation and I would rather not do that.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2006-07-19 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 6:50 michael_mic in crypto api? Michael Wu
2006-07-14 7:23 ` Michael Wu
2006-07-15 10:37 ` Herbert Xu
2006-07-16 4:44 ` Michael Wu
2006-07-19 15:39 ` Herbert Xu
2006-07-19 16:19 ` Jouni Malinen [this message]
2006-07-19 17:05 ` Herbert Xu
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=20060719161913.GA15317@instant802.com \
--to=jkm@devicescape.com \
--cc=flamingice@sourmilk.net \
--cc=herbert@gondor.apana.org.au \
--cc=jbenc@suse.cz \
--cc=jkmaline@cc.hut.fi \
--cc=linville@tuxdriver.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).