Hi Dave! The first thing I would look into would be to use 2.2.17.10. Then, if you have configured as modules, make sure you have them loaded. Also, make sure the cryptoapi is functioning (look at /proc/crypto/ciphers/; the cipher you want to use should be listed there.) If these do not help, please send a complete command history of what you did. Marc dave@xxxxxxxxxxxxxxxxxxxxxx wrote: > > Hi Marc, > > I've been trying to get loopback encryption working. Details: > > kernel: 2.2.17 > international patch: 2.2.17.9 > util-linux: 2.10p > > I've followed the instructions as follows: > > - patch kernel source > - configure and build kernel > - reboot with new kernel > - patch util-linux > - build and install mount, umount, losetup > > However, when I try to do losetup I get one of the errors reported in > the 'frequently asked questions' section of your Encryption HOWTO: > > ioctl: LOOP_SET_STATUS: Invalid argument > > I've checked that this happens with each of the following ciphers: > > idea, DES, blowfish, twofish, cast128, serpent, mars > > which suggests its something fundamental. > > I've tried searching for a solution on the web, but have found nothing > particularly clear. There are a lot of posts about DES doing something > funny with getpass, but no indication that this would cause a problem > with the other ciphers. There were some posts in 1999 about there > being a fundamental incompatibility between the kernel and libc-2.0 > regarding the definition of dev_t, which could cause problems with > loopback mounts. (My libc is at version 2.0.7.) > > Any ideas? > > Thanks, > Dave. Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
