[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
yet another 2.4.22 INsuccess story
Hi,
I've been using kerneli.org's patch-int for a year now, and everything
has been running perfectly until now. I have several kerneli.org
encrypted volumes, which stopped working with 2.4.22's new cryptoapi
stuff. I've been reading the threads on this issue, and unfortunately
I'm unable to mount old volumes with a 2.4.22 kernel.
Below are the descriptions of my attempts. I don't expect a HOWTO to
make it work, just a couple of your brain-time to help on finding the
problem.
BTW, to make sure I don't have a patch-int legacy problem, I've created
a brand new crypto-fs using 2.4.21 and the corresponding patch-int,
which I'm using in these tests.
strike 1:
---------
linux-2.4.22
patch-cryptoloop-jari-2.4.22-rc2.0 / 1
util-linux-2.12
losetup-keygen-prog-mk7
losetup-variable-key-size-mk6
hashalot
hashalot ripemd160 | losetup -p0 -e aes-cbc-256 /dev/loop0
~scorpio/TESTE
mount -o loop /dev/loop0 ~scorpio/teste
VFS: Can't find a valid FAT filesystem on dev ...
strike 2:
---------
linux-2.4.22
loop-AES-v1.7e
util-linux-2.12
losetup-keygen-prog-mk7
losetup-variable-key-size-mk6
losetup -p0 -e aes-cbc-256 /dev/loop0 ~scorpio/TESTE
ioctl: LOOP_SET_STATUS: Invalid argument
Thanks in advance.
Best of regards,
Ricardo Oliveira.
--
Ricardo Manuel Oliveira
Eurotux Informtica, SA
Tel: +351 253257395 // +351 919475934
Fax: +351 253257396
-
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/