https://bugzilla.novell.com/show_bug.cgi?id=655804 https://bugzilla.novell.com/show_bug.cgi?id=655804#c2 --- Comment #2 from Ludwig Nussel <lnussel@novell.com> 2010-11-30 08:48:47 CET --- (In reply to comment #1)
Obvious fix: --- mount/lomount.c.orig 2010-11-29 11:44:05.000000000 +0100 +++ mount/lomount.c 2010-11-29 11:44:26.000000000 +0100 @@ -822,8 +822,7 @@ set_loop(const char *device, const char
if(!loopinfo64.lo_encrypt_key_size) { if(!keysz) { - if(verbose) - fprintf(stderr, _("please specify a key length\n")); + fprintf(stderr, _("please specify a key length\n")); return 1; } loopinfo64.lo_encrypt_key_size = keysz>>3;
Ack.
Apart from that, I don't know how to use the -k/-e anyway:
# losetup -v -e aes -k 256 /dev/loop0 file Password: ioctl: LOOP_SET_STATUS: Invalid argument
(file was created as dd if=/dev/zero of=file ...). Is this supposed to work?
You need to modprobe cryptoloop
Ludwig, the most important question is if we want to retain this patch in future openSUSE/SLE versions. As far as I see, it has been rejected by upstream u-l-ng because cryptoloop is considered deprecated (in favor of cryptsetup??).
In theory it's deprecated, yes. Last time I tried to get rid of the old patch (ie 3 years ago) there were still people that had encrypted loop images in /etc/fstab. I think even today cryptoloop is still the only way to allow users to mount encrypted images. The integration of dmcrypt into mount never happened. So SUSE and Debian kept that patch. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.