-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 28 February 2002 21:42, IT3 Stuart Blake Tener, USNR-R wrote: > I never said you had an issue with giving users a choice of > algorithms to choose from, I am just stating that cryptoapi needs to > become a permanent part of the Linus kernel before people will begin > to accept it. Wrong. People start to accept is _now_. Take PPDD, take the NFS implementation announced Tuesday. CIPE and FreeS/WAN are at least considering the move. > As it is now, every time I rebuild my kernel, I need to build, > install and merge the NVIDIA drivers, and the ltmodem drivers. Sorry, but that is how it works in Linux. I had to merge new-style RAID, ext3 and kerneli back when I built by own kernels (and I did that evry few days...) > In other words if knowing what kernel version cryptoapi works > with can be more complicated than any kernel after version x.y.z, > then it will not be an easily deployable patch. No patch that adds a new API to the kernel applies to more than a few minor releases in a row. The kerneli patch on 2.2 was remarkable stable w.r.t. to applicability to different kernels. Now that 2.4 has somewhat settled, I expect that same to hold. > Does your cryptoapi > work flawlessly with a Linus kernel of 2.4.18, or 2.4.19pre1? It's a Marcelo kernel, BTW ;-) Marc PS: Please trim your quotes. - -- Marc Mutz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8fqxB3oWD+L2/6DgRAr6hAKDMtk/E51GMYfdU4Xs/Tdy6Giwn5gCcDWC2 xPzoDHy/3RiKb1qhZ49VEi0= =1PkD -----END PGP SIGNATURE----- - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/