Hmm, I just checked, and I get the same thing when trying to create a new encrypted filesystem: [root@lain /root]# dd if=/dev/urandom of=crypto-test bs=1M count=50 50+0 records in 50+0 records out [root@lain /root]# losetup -e aes -k 192 /dev/loop0 /root/crypto-test Password : The cipher does not exist, or a cipher module needs to be loaded into the kernel ioctl: LOOP_SET_STATUS: Invalid argument Here is what I have in /proc/crypto: [root@lain /root]# ls -R /proc/crypto/ /proc/crypto/: cipher digest /proc/crypto/cipher: aes-cbc aes-ecb blowfish-cbc blowfish-ecb serpent-cbc serpent-ecb /proc/crypto/digest: md5 sha1 Is there a problem with the util-linux patch I'm using? (I think that its version 2.11h) Or is this version of the patch just foobared? Chris Schadl [17/02/02 13:39 -0600]: > Hi, > > I have a large amount of data which was encrypted via the old cryptoapi > (2.4.7.0) modules. Since then, I've decided to try out the new international > crypto patch. However, when I try to access my old cryptoapi data, I get the > following error: > > [root@lain /]# mount -t iso9660 -o encryption=aes,loop /dev/cdrom /cdrom > Available keysizes (bits): 128 192 256 > Keysize: 192 > Password : > The cipher does not exist, or a cipher module needs to be loaded into the > kernel > ioctl: LOOP_SET_STATUS: Invalid argument > > I do have the cryptoloop and cipher-aes modules loaded. Is it going to be > possible to access my old cryptoapi encrypted data with the new patch-int? > > -- > Chris Schadl > cschadl@satan.org.uk > > - > Linux-crypto: cryptography in and on the Linux system > Archive: http://mail.nl.linux.org/linux-crypto/ > -- Chris Schadl cschadl@satan.org.uk - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
