[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Encrypted loopback filesystem

* Michael S. Peek <peek@tiem.utk.edu> [2007-05-25 10:43:26 -0400]:

> Hi gurus,
> I thought I would experiment with creating an encrypted loopback 
> filesystem.  I've generated a file of random numbers, but I can't attack 
> it to /dev/loop0:
> # losetup -e serpent /dev/loop0 $(pwd)/file.bin
> Password:
> ioctl: LOOP_SET_STATUS: Invalid argument
> I did a quick google search, but what I've found refers to making sure 
> that you have the modules and util-linux installed, and I 've got those 
> (using Debian/Etch), and the loop and serpent modules are loaded.
> What else can I check for?

loop-aes-modules-XXX (looks like you have them)

after install of loop-aes-modules, module loop must be removed and then
reloaded in the kernel to get to the new loop-aes module (only once if
you haven't rebooted since install:

rmmod loop
modprobe loop

command would be:

losetup -e serpent[128,192, or 256] /dev/loop[1,2,3,4,5,6,7, or 8]\

 file.bin must have a physical size already, example:

 dd if=/dev/urandom of=~/file.bin bs=1024 count=1000

 will block out a working space for the file... change the count to vary
 the size...

Look here:


And here:


Good place to start.  Good luck!


... In Brooklyn, we had such great pennant races, it made the World Series
    just something that came later.
		    -- Walter O'Malley, Dodgers owner

Reply to: