Can't make losetup mount a crypto file to the loopback device (SuSE 8.2)
I'm trying to mount a file to the loopback device but the losetup command complains about it. I'm using the command line: losetup -e twofish /dev/loop0 /root/testfile losetup asks for a password but returns: ioctl: LOOP_SET_STATUS: invalid argument when one is entered "losetup -e none" works I have tried with the standard kernel in SuSE 8.2 but also kernel 2.4.20-13 with both "loopback device support" and "Twofish encryption for loopback device" compiled into the kernel. Any suggestions. Thanks in advance Bo Jacobsen
On Wednesday 30 Apr 2003 22:51, Bo Jacobsen wrote:
I'm trying to mount a file to the loopback device but the losetup command complains about it.
I'm using the command line: losetup -e twofish /dev/loop0 /root/testfile
losetup asks for a password but returns: ioctl: LOOP_SET_STATUS: invalid argument when one is entered
I think I recognise this one; I seem to remember that you have to make sure your losetup is the "international" one, with encryption support compiled in. I think I got around it by building the international version of util-linux (I seem to have the source here, so I must have patched it and compiled it myself at some point) and installing those versions of losetup/mount instead of the system ones. The last time I got a kernel update I had to patch the kernel to make it the international version, too, but all this might just be because I'm still plugging away on suse 7.2... All this was quite some time ago, though, so my memory may be playing tricks on me. I do have it working with twofish here, though. M -- "It's the small gaps between the rain that count, and learning how to live amongst them." -- Jeff Noon
I had this same problem and the solution was rather simple, the module for twofish wasnt loaded. do a lsmod and look for: loop_fish2 9120 0 If its not there, then do a insmod loop_fish2 and it all should work. Adam On Wed, Apr 30, 2003 at 11:51:25PM +0200, Bo Jacobsen wrote:
I'm trying to mount a file to the loopback device but the losetup command complains about it.
I'm using the command line: losetup -e twofish /dev/loop0 /root/testfile
losetup asks for a password but returns: ioctl: LOOP_SET_STATUS: invalid argument when one is entered
"losetup -e none" works
I have tried with the standard kernel in SuSE 8.2 but also kernel 2.4.20-13 with both "loopback device support" and "Twofish encryption for loopback device" compiled into the kernel.
Any suggestions.
Thanks in advance Bo Jacobsen
-- Technical Consultant ----------------------------------------------------------------------- FORENSIC DATA SERVICES PTY LIMITED http://www.forensicdata.com.au ------------------------------------------------------------------------ The information contained in this e-mail is confidential and is intended solely for the addressee. If you received this e-mail by mistake please notify us immediately and delete all copies of this message. You must not disclose or use in any way the information in the e-mail. It is the responsibility of the recipient to virus scan this e-mail and any attachments included.
On Thursday 01 May 2003 04:41, Adam Daniel wrote:
I had this same problem and the solution was rather simple, the module for twofish wasnt loaded.
Having thought about this since I posted my original reply, this kind of solution does seem more likely, in fact. If losetup is calling an ioctl that the kernel hasn't heard of, it makes more sense to assume that losetup is the international version, and it's the kernel that has the problem. I have the cryptography stuff compiled straight in rather than modular, so that's why I don't see the problem. M -- "It's the small gaps between the rain that count, and learning how to live amongst them." -- Jeff Noon
Yes this seems to be the problem, but it does not explain everything. I tried to compile the "loopback device support" and "Twofish encryption for loopback device" options as modules instead and THEN the losetup command worked (after "insmod loop_fish2"e) so apparently there is a problem if they are compiled, not as a modules, but as a part of the kernel. Bo
I had this same problem and the solution was rather simple, the module for twofish wasnt loaded.
do a lsmod and look for:
loop_fish2 9120 0
If its not there, then do a insmod loop_fish2 and it all should work.
Adam
On Wed, Apr 30, 2003 at 11:51:25PM +0200, Bo Jacobsen wrote:
I'm trying to mount a file to the loopback device but the losetup command complains about it.
I'm using the command line: losetup -e twofish /dev/loop0 /root/testfile
losetup asks for a password but returns: ioctl: LOOP_SET_STATUS: invalid argument when one is entered
"losetup -e none" works
I have tried with the standard kernel in SuSE 8.2 but also kernel 2.4.20-13 with both "loopback device support" and "Twofish encryption for loopback device" compiled into the kernel.
Any suggestions.
Thanks in advance Bo Jacobsen
--
Technical Consultant ----------------------------------------------------------------------- FORENSIC DATA SERVICES PTY LIMITED http://www.forensicdata.com.au ------------------------------------------------------------------------ The information contained in this e-mail is confidential and is intended solely for the addressee. If you received this e-mail by mistake please notify us immediately and delete all copies of this message. You must not disclose or use in any way the information in the e-mail. It is the responsibility of the recipient to virus scan this e-mail and any attachments included.
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
participants (3)
-
Adam Daniel -
Bo Jacobsen -
Matt Gibson