hello! I've prepared a few ready to use cryptoapi rpms for use with redhat-8.0, which should have been released by today officially -- so finally, you _really_ don't need to 'modify' your rh stock loop-driver at all... you don't even have to recompile anything or even reboot... fyi, redhat-8.0 stock kernel is being shipped with cryptoapi.o, cryptoloop.o, a loop-iv patched (alas not jari's loop fixes -- so better don't swap over the loop device!) loop.o and the cipher-aes.o ansi-c implementation, all compiled as modules; what's missing it's a cryptoapi enabled util-linux rpm, which you'll find at the below mentioned URL folder; if you want other ciphers, I've prepared a few kernel-cryptoapi-addon rpms which have been built against the 2.4.18-14 kernel rpms ksyms; (make sure you pick the right one matching your arch, otherwise you'll get unresolved symbols from depmod) I've also prepared some ipsec_tunnel rpms, based on the 2002-09-29 snaphost -- thus handle with care! ;-) I'm also trying to find out a _clean_ way to override the default cipher-aes.o module shipped with rh8, in order to prepare some 100%-performance boosting kernel-cipher-aes-i586 rpm (based on http://www.ifs.tuwien.ac.at/~hvr/crypto/cipher-aes-i586-0.3.tar.gz, which you might want to build yourself for the meantime, until I figure out some way to rpm it...) and here the URL where you can find all mentioned redhat-8.0 related rpms: http://www.ifs.tuwien.ac.at/~hvr/crypto/redhat-8.0/ == it might be noteworthy, that cryptoapi-0.1.0-rc3 has been released; the main difference to -rc2 is a fixed digest-md5.c implementation; http://www.ifs.tuwien.ac.at/~hvr/crypto/cryptoapi-0.1.0-rc3.tar.bz2 http://www.kernel.org/pub/linux/kernel/crypto/v2.4/testing/cryptoapi-0.1.0-rc3.tar.bz2 == I've also wrapped up cryptoapi-0.1.0-rc3, cryptoloop-0.0.1-pre1 and ipsec_tunnel-2002-09-29 into an unified patch-int-2.4.19.2: get it here: http://www.ifs.tuwien.ac.at/~hvr/crypto/patch-int-2.4.19.2.bz2 http://www.kernel.org/pub/linux/kernel/crypto/v2.4/testing/patch-int-2.4.19.2.bz2 == disclaimer: Since I cannot make sure with reasonable effort, that the code published works under all possible configurations, you're expected to take precautionary steps, in order to avoid data-loss in case of malfunction... i.e. make the usual backups... ;) regards, -- Herbert Valerio Riedel / Phone: (EUROPE) +43-1-58801-18840 Email: hvr@hvrlab.org / Finger hvr@gnu.org for GnuPG Public Key GnuPG Key Fingerprint: 7BB9 2D6C D485 CE64 4748 5F65 4981 E064 883F 4142
This is a digitally signed message part