Ah, yeah. About 5 minutes after I posted this I discovered that a seperate
module 'cryptoloop' is created. Once I loaded that, everything worked fine.
Max Vozeler [31/01/06 20:32 +0100]:
> Hi Chris,
>
> On Tue, Jan 31, 2006 at 12:42:37PM -0600, Chris Schadl wrote:
> > I've successfully compiled the modules and installed
> > the loop-aes-utils package, but when I try to mount the data I
> > get the following error:
> >
> > # mount -o loop,encryption=aes192 /dev/hdb /media/cdrom
> > Password:
> > ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (192 bits) not supported by kernel
>
> This suggests that you have the kernel loop module loaded instead
> of the loop-AES version. Did you try to unload the loop module in
> case the kernel version was already loaded before you installed
> loop-AES? ("rmmod loop; modprobe loop")
>
> What does the output of "lsmod | grep loop" show?
>
> > The weird thing is that according to /proc/crypto, the maximum AES keysisize
> > is 32 bits...
>
> The value should be in bytes, no need to worry ;) /proc/crypto also
> lists the in-kernel cryptoapi ciphers, which loop-AES doesn't use.
> It provides and uses it's own implementation of the AES cipher.
>
> cheers,
> Max
>
> -
> Linux-crypto: cryptography in and on the Linux system
> Archive: http://mail.nl.linux.org/linux-crypto/
--
Chris Schadl
cschadl@xxxxxxxxxxxx
-
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/
