|
[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
[NMLUG] encrypted loopback filesystems
- Subject: [NMLUG] encrypted loopback filesystems
- From: _sarang_ at sarangworld.com (Sarang)
- Date: Wed Jan 5 13:13:27 2005
- In-reply-to: <41DC3424.3030208@harrisdev.com>
Dumb questions:
% Did you try "losetup -e NONE"?
% Did you try "mke2fs filename" and then "mount -o loop -t ext2 filename /mnt"
instead of losetup?
--
Sincerely, Sarang (sarang@sarangworld.com)
AOL Instant Messenger ID: JavaMath
Backup Email: saranghome@softhome.net
<html><img src='http://noproxy.sarangworld.com/EXP/rr.php?20050105.130656'></html>
On Wed, 5 Jan 2005, Jody Harris wrote:
> Date: Wed, 05 Jan 2005 11:38:28 -0700
> From: Jody Harris <havoc@harrisdev.com>
> Reply-To: New Mexico Linux Users Group Mail List <nmlug@nmlug.org>
> To: New Mexico Linux Users Group Mail List <nmlug@nmlug.org>
> Subject: [NMLUG] encrypted loopback filesystems
>
> Using dd, I created an empty "disk image."
>
> I then attempted to use losetup to create an filesystem on that image,
> but I keep getting:
> ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length
> (128 bits) not supported by kernel
>
> So, I recompiled the kernel with all of the crypto options turned on.
> Even with the new kernel, I'm still getting the "not supported" message.
>
> Apparently, I overlooked something in the kernel configuration. What
> should I be looking for?
>
> thanks,
> jody
> --
> http://www.RealizationSystems.com/ -- start communicating
> http://www.GalacticSlacker.com/ -- read it and weep
> http://www.NMPerspective.com/ -- a Southwest Perspective
> _______________________________________________
> NMLUG mailing list
> NMLUG@nmlug.org
> http://www.nmlug.org/mailman/listinfo/nmlug
>
|
|
