I was using linux kernel 2.4.21 prior to now. I had patched it with one of the crypto patches. I forget what I had to do to get that to work. It was difficult. But it was working. I was able to create an encrypted filesystem using the loopback device. Great.
But recently I had to grab the linux 2.4.26 kernel to support my new motherboard. It has cryptoapi already in there. I turned on all of the crypto modules. I compiled the kernel and rebooted. But alas, losetup reported that it doesn't recognize "aes" as a valid crypto cipher. I'm actually using blowfish and aes, by the way. Both of them don't work. When I cat /proc/crypto, it shows all of the crypto ciphers are loaded in the kernel, by the way.
So what do I have to do to get kernel 2.4.26 to the point where I can create an encrypted filesystem? I don't care too much about backwards compatibility. Does anyone have a step by step list of instructions on how to do that?
I know there's something about grabbing and possibly having to patch the util-linux stuff so that it can use the crypto ciphers? Do we have to do that with this kernel? Which util-linux version should I be using?
Then there's something about cryptoloop patches?
Very confused.
Thanks, Steve
_________________________________________________________________
MSN Movies - Trailers, showtimes, DVD's, and the latest news from Hollywood! http://movies.msn.click-url.com/go/onm00200509ave/direct/01/
- Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
