-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi list,
i experienced problems as I updated my kernel-2.4.21 patched with "patch-int-2.4.21" and "loop-jari-2.4.21" as described in: http://www.symlink.dk/linux/cryptofs.php
with kernel-2.4.22 with integrated cryptoapi support.
I compiled the new kernel 2.4.22 like: CONFIG_CRYPTO=y # CONFIG_CRYPTO_HMAC is not set CONFIG_CRYPTO_NULL=m CONFIG_CRYPTO_MD4=m CONFIG_CRYPTO_MD5=m CONFIG_CRYPTO_SHA1=m CONFIG_CRYPTO_SHA256=m CONFIG_CRYPTO_SHA512=m CONFIG_CRYPTO_DES=m CONFIG_CRYPTO_BLOWFISH=m CONFIG_CRYPTO_TWOFISH=m CONFIG_CRYPTO_SERPENT=m CONFIG_CRYPTO_AES=m # CONFIG_CRYPTO_DEFLATE is not set # CONFIG_CRYPTO_TEST is not set - ---
When I now try to mount my existing loop volume like:
/sbin/losetup -e aes -k 128 /dev/loop0 /dev/hda1
or when i try to mount a file manually with:
dd if=/dev/urandom of=test bs=512 count=20480 /sbin/losetup /dev/loop0 test -e blowfish
I get the following error: !!
The cipher does not exist, or a cipher module needs to be loaded into the kernel ioctl: LOOP_SET_STATUS: Invalid argument
If I do a "lsmod" I see the blowfish module (unused)
I use the patched "util-linux-211r-10int.i386.rpm" as well as "losetup-2.11r-10int.i386.rpm" and "mount-2.11r-10int.i396.rpm". (with RedHat 9)
Do I have to use newer versions of these programms ??
What about: http://www.kernel.org/pub/linux/kernel/crypto/v2.4/testing/patch-aes-asm-2.4.22.0 http://www.kernel.org/pub/linux/kernel/crypto/v2.4/testing/patch-cryptoloop-jari-2.4.22.0
Do I need this ones additionally ?
Hopefully someone could bring some insight on this topic ?
thanxx
jan
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/UPzLsWMlW7B41goRAuXsAJwOrpTnJITifQgnjkuMOiFxUjzR1QCaAt// s7juEVhUOPP+6uiCnq+D4R0= =ujKT -----END PGP SIGNATURE-----
- Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/