Pb deciphering after 2.4.21 -> 2.4.23 upgrade

[fchabaud@free.fr]

Hi all,

I'm sorry to ask a question that must have a simple answer but despite
careful reading of the archive, I didn't succeed in deciphering
partitions after upgrade from 2.4.21 to 2.4.23.

My configuration before upgrade:
2.4.21-pre4 with a few patches (acpi, swsusp) including
loop-hvr-2_4_18_1.patch
patch-int-2.4.18.3.bz2

losetup compiled from 
 util-linux-2.11u.tar.bz2
 util-linux-2.11r.patch.bz2
mount version 2.11u (I don't remember if it results from the compilation
of above or if it's the mandrake 9.0 version)

I use a bunch of scripts using gpg to store password phrase on an usb
keys. The following just worked correctly:
losetup --encryption aes --keybits 256 --phash sha256 /dev/loop7 /dev/sda4 < keyfile
and in the auto.usb automount file
cipher          -fstype=ext3            :/dev/loop7

Now, I have upgraded to:
2.4.23 with patch swsusp
From what I understand there's no more need to use international patch
nor hvr loop patch but I included
patch-aes-asm-2.4.22.0

losetup was recompiled from
 util-linux-2.12.tar.gz
 losetup-variable-key-size-mk6.patch
 losetup-keygen-prog-mk7.patch

I also downloaded and compiled
 hashalot-0.1.0.tar.gz

After installing all these, I loaded aes module
cat /proc/crypto
name         : aes
module       : aes
type         : cipher
blocksize    : 16
min keysize  : 16
max keysize  : 32
ivsize       : 16


then tried
hashalot-0.1.0/hashalot sha256 < keyfile | losetup -p 0 -e aes-256 /dev/loop7 /dev/sda4
but I obtained 
ioctl: LOOP_SET_STATUS: Invalid argument
I also tried 
hashalot-0.1.0/hashalot sha256 < keyfile | losetup -p 0 -e aes-cbc-256 /dev/loop7 /dev/sda4
with same result and even 
hashalot-0.1.0/hashalot sha256 < keyfile | losetup -p 0 -e aes /dev/loop7 /dev/sda4
which gives 
You must specify a key size (in bits) for use with CryptoAPI encryption.

After that, I tried to apply patch-cryptoloop-jari-2.4.22.0 to kernel. I
noticed that a new cryptoloop option appears. As it disables crypto
ciphers if enabling it I let it disabled. This time, the losetup seemed
to function but then fsck.ext3 -n /dev/loop7 never succeeded in finding
a superblock. 

It seems to me that cryptoapi is installed but I must miss something.
I'm not sure jari patch is needed since I never used it before.

Thanks for any help.


Florent Chabaud
gpg: 28C9 9E1A 5507 5574 EDE6  2E8F 2B37 D83F 95C8 1C3C
http://www.carva.org/florent.chabaud | florent.chabaud@m4x.org

-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/