Messages in this thread | | | Date | Wed, 14 May 2003 17:59:04 -0700 | From | Jouni Malinen <> | Subject | Re: airo and firmware upload (was Re: 2.6 must-fix list, v3) |
| |
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).
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.
-- Jouni Malinen PGP id EFC895FA - 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/
| |