From: Jeff Garzik <jgarzik@pobox.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: jt@hpl.hp.com,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@digeo.com>,
David Gibson <hermes@gibson.dropbear.id.au>,
Benjamin Reed <breed@almaden.ibm.com>,
Javier Achirica <achirica@ttd.net>,
Jouni Malinen <jkmaline@cc.hut.fi>
Subject: Re: airo and firmware upload (was Re: 2.6 must-fix list, v3)
Date: Wed, 14 May 2003 19:53:31 -0400 [thread overview]
Message-ID: <3EC2D6FB.5050700@pobox.com> (raw)
In-Reply-To: <20030514234359.GB9898@suse.de>
Dave Jones wrote:
> On Wed, May 14, 2003 at 04:32:35PM -0700, Jean Tourrilhes wrote:
>
> > While we are on the subject : a few months ago, Javier added
> > support for MIC to the airo driver. It's basically crypto based on
> > AES. You refused to include that part in the kernel because crypto was
> > not accepted in the kernel.
> > Fast forward : today we have crypto in the 2.5.X kernel. Does
> > this mean that you would have no objection accepting a patch from
> > Javier including the crypto part ?
>
> Sounds like it would be better to get it using the in-kernel crypto
> stuff rather than reimplementing its own routines. Same for the HostAP
> driver.
Correct.
_I_ didn't refuse the crypto, Linus did. But that was a positive step,
that kicked off inclusion of crypto into the kernel.
airo and HostAP do indeed need to use CryptoAPI not reimplement their
own crypto, though...
Jeff
next prev parent reply other threads:[~2003-05-14 23:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 21:12 2.6 must-fix list, v3 Jean Tourrilhes
2003-05-14 22:06 ` airo and firmware upload (was Re: 2.6 must-fix list, v3) Jeff Garzik
2003-05-14 23:32 ` Jean Tourrilhes
2003-05-14 23:38 ` Andrew Morton
2003-05-15 1:04 ` David Gibson
2003-05-16 7:27 ` Manuel Estrada Sainz
2003-05-14 23:43 ` Dave Jones
2003-05-14 23:53 ` Jeff Garzik [this message]
2003-05-15 0:59 ` Jouni Malinen
2003-05-15 2:20 ` Jean Tourrilhes
2003-05-15 6:16 ` James Morris
2003-05-15 1:02 ` Jean Tourrilhes
2003-05-15 4:21 ` CryptoAPI and WEP/stream ciphers (was: airo and firmware upload) Jouni Malinen
2003-05-15 6:04 ` James Morris
2003-05-15 0:55 ` airo and firmware upload (was Re: 2.6 must-fix list, v3) Jean Tourrilhes
2003-05-15 7:13 ` Greg KH
2003-05-15 17:24 ` Jean Tourrilhes
2003-05-15 17:46 ` Greg KH
2003-05-15 19:55 ` Jean Tourrilhes
2003-05-15 20:10 ` Greg KH
2003-05-17 16:58 ` 2.6 must-fix list, v3 Pavel Machek
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=3EC2D6FB.5050700@pobox.com \
--to=jgarzik@pobox.com \
--cc=achirica@ttd.net \
--cc=akpm@digeo.com \
--cc=breed@almaden.ibm.com \
--cc=davej@codemonkey.org.uk \
--cc=hermes@gibson.dropbear.id.au \
--cc=jkmaline@cc.hut.fi \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@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