Hi! I am running Suse 10.1 and tried to setup an encrypted loopback device like this: dd if=/dev/urandom of=testfile bs=1M count=10 losetup /dev/loop0 testfile Before proceeding, I modprobed dm-mod,dm-crypt,aes,sha1,sha256, downloaded, compiled and installed the luks-enabled cryptsetup tool. Running dmsetup targets shows that the crypto target is present, catting proc/crypto shows that all modules were successfully loaded. Executing cryptsetup -c aes-cbc-essiv:sha256 -y -s 256 luksFormat /dev/loop0 works fine and cryptsetup -v luksDump /dev/loop0 shows that the meta data was created. However, running cryptsetup luksOpen /dev/loop0 cryptfs first prompts for the password, but it does not return. No entry in /dev/mapper is created. Does somebody on this mailing list has a clue what is going wrong? The only thing that I noticed is that on Suse the /dev/mapper/control is a symbolic link to crw-rw---- 1 root root 10, 63 Jan 1 1970 /dev/device-mapper I don't know if this is correct. What other reason could there be for luksOpen to fail (without any error message) Thanks, Dierk _______________________________________________________________________ Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos. Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=022222 --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
