Date: Wed, 14 May 2003 19:20:34 -0700
To: Jouni Malinen <jkmaline@cc.hut.fi>
Cc: Jeff Garzik <jgarzik@pobox.com>, Dave Jones <davej@codemonkey.org.uk>,
       jt@hpl.hp.com, Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: airo and firmware upload (was Re: 2.6 must-fix list, v3)
Message-ID: <20030515022034.GA12608@bougret.hpl.hp.com>
Reply-To: jt@hpl.hp.com
References: <20030514211222.GA10453@bougret.hpl.hp.com> <3EC2BDEC.6020401@pobox.com> <20030514233235.GA11581@bougret.hpl.hp.com> <20030514234359.GB9898@suse.de> <3EC2D6FB.5050700@pobox.com> <20030515005904.GA1510@jm.kir.nu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030515005904.GA1510@jm.kir.nu>
User-Agent: Mutt/1.3.28i
Organisation: HP Labs Palo Alto
Address: HP Labs, 1U-17, 1501 Page Mill road, Palo Alto, CA 94304, USA.
E-mail: jt@hpl.hp.com
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1885
Lines: 43

On Wed, May 14, 2003 at 05:59:04PM -0700, Jouni Malinen wrote:
> On Wed, May 14, 2003 at 07:53:31PM -0400, Jeff Garzik wrote:
> 
> > airo and HostAP do indeed need to use CryptoAPI not reimplement their 
> > own crypto, though...
> 
> Host AP driver has a dynamic crypto implementation that allows one to
> load new algorithms as a separate kernel modules. One of such modules
> was an interface to use CryptoAPI. However, I don't think there is a
> public release of it.
> 
> Do you think WEP should be implemented as a CryptoAPI algorithm? It is a
> combination of CRC-32 and RC4 and the crypto module in Host AP does
> these together in one pass of the packet payload to minimize host CPU
> load. I'm not keen on using RC4 separately with CryptoAPI (I don't think
> it is even included yet) if that means making the WEP encryption use
> more CPU.. However, I could consider taking CryptoAPI into use it would
> support WEP as an algorithm (i.e., I could consider porting the current
> Host AP WEP code to CryptoAPI).

	There is no RC4 currently in the crypto API (guess why), and I
believe that most wireless driver would be interested in the RC4+CRC,
so I would advocate for doing "WEP".

> Since I'm not that interested in maintaining multiple source trees of
> the driver, own WEP implementation is going to remain in the Host AP
> driver for 2.2 and 2.4 kernels. Anyway, this could probably be
> automatically stripped from the code if backward compatibility in
> drivers must be removed from 2.5/2.6 kernel tree.

	If you define the WEP in the kernel crypto, it could even be
the exact same file.

> Jouni Malinen

	Thanks...

	Jean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/