Peter, et al.: As I have said in previous posts, having the core of the crypto API (absent the actual modules that do the encryption) in the core kernel (non I-patch) makes sense. The regular kernel could be distributed with dummy modules that do no encryption, that just pass back the same clear text they were passed, thus unifying the two kernel source trees. Then only creation of specific "plug-in" encryption modules would be necessary, with people just going and replacing the dummy modules with real encryption modules for each type of encryption so written. Perhaps, have a single module inclusive of all the encryption technologies developed thus far would further reduce confusion. If we had, a single module that needed to be replaced (from the alleged dummy one the regular kernel would provide) which had all the encryption technologies in it, then using the I-patch would get much simpler. I still don't know what is broken in the I-patch. Very Respectfully, Stuart Blake Tener, IT3, USNR-R, N3GWG VTU 1904G (Volunteer Training Unit) stuart@xxxxxxxxxxx west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. Sunday, July 08, 2001 6:35 PM -----Original Message----- From: owner-linux-crypto@xxxxxxxxxxxx [mailto:owner-linux-crypto@xxxxxxxxxxxx]On Behalf Of peter k. Sent: Sunday, July 08, 2001 11:02 AM To: Herbert Valerio Riedel Cc: linux-crypto@xxxxxxxxxxxx Subject: Re: Announce loop-AES-v1.3b file crypto package > the international crypto patch has received a bit of criticism few months > ago, so I became a bit unmotivated... > > ...but if there is enough demand I would work on it again and try to fix > some of the bigger show stoppers, but I don't want to replace Alexander > Kjeldaas if he's still working on the official international crypto patch, > and maybe he has already some unreleased fixes waiting... > > the plans were, if I remember correctly, to make the crypto api that > generic as to allow other kernelspace projects making use of encryption, > most prominently network encryption projects, to use the crypto api as a > common cipher repository... or to put it in other words, to implement > kernel encryption services, maybe even allow support for ciphers > implemented in hardware... IMHO there HAS TO BE full crypto stuff in the kernel and full support for encrypting file systems as those features are very useful if the current international crypto patch isnt ok then there should be a new one created, but not having crypto features officially in the kernel sux =( Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
