From: Michael Wu <flamingice@sourmilk.net>
To: Jiri Benc <jbenc@suse.cz>
Cc: "John W. Linville" <linville@tuxdriver.com>, netdev@vger.kernel.org
Subject: Re: michael_mic in crypto api?
Date: Fri, 14 Jul 2006 00:23:41 -0700 [thread overview]
Message-ID: <200607140023.48727.flamingice@sourmilk.net> (raw)
In-Reply-To: <200607132350.25755.michael.wu@mozilla.com>
[-- Attachment #1: Type: text/plain, Size: 425 bytes --]
On Thursday 13 July 2006 23:50, Michael Wu wrote:
> Is there really a point to having michael_mic in crypto api? The only users
> are 802.11 stacks. I can imagine arc4 being used for other purposes, but
> michael_mic is very much wireless only. The only advantage of keeping
> michael_mic in crypto seems to be the testing code.
>
> -Michael Wu
Err, sent from the wrong address. Opps. Too many email addresses..
-Michael Wu
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-07-14 7:24 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 [this message]
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
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=200607140023.48727.flamingice@sourmilk.net \
--to=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--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).