[CryptoAPI-devel] Proposal

[Kyle M. <ky...@de...>]

After having looked through alot of the cipher code again tonight, I
feel it would be a good idea to rework ^ rewrite the ciphers to follow a
proper framework. Keep in mind I mean the ciphers themselves, not
CryptoAPI. For example: all the different cipher contexts have different
names internal to them, and I propose we transition them to a consistent
naming scheme.

After doing this, I believe we will have better control over the cipher
implementations, and a standard set for ciphers which others may
contribute to the project.

I also propose that we begin looking at adding assembler optimization to
as many of the ciphers, for as many platforms as possible. I'm not quite
sure what the best way to implement this would be though, as it has been
mentioned that Linus does not like bloating include/asm-platform
directories any more than already.

Since this is all under the hood, it can wait until after we make a new
release at the end of the first week of April.

PS: We should also get in touch with the FreeS/WAN fellows, and some
other projects that could make use of our crypto.

  - k
--=20
copyleft (c) 2002, Kyle McMartin