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...
I tried to change my WEP implementation to use CryptoAPI, but that ended
up in problems.. If I understood correctly, current CryptoAPI supports
only block ciphers(?). However, WEP uses RC4 as a stream cipher. This
does not seem to fit the cipher definition in CryptoAPI. One might be
able to implement it as an compression algorithm (encrypt as decompress,
since it adds IV and ICV; and decrypt as compress). However, this
certainly does not sound very reasonable.. Another alternative would be
to add support for stream ciphers into CryptoAPI.
Do you think that it would still be required to get rid of the own WEP
implementation in the Host AP driver before including it into the kernel
tree? Would this mean that someone would first need to add support for
stream ciphers into CryptoAPI? Any change of that happening for Linux
2.6.x?
And one more question before using more time with WEP implementation..
Is someone already working with stream cipher support for CryptoAPI?
-- 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/
This archive was generated by hypermail 2b29 : Thu May 15 2003 - 22:00:55 EST