Hi guys,
2 years ago I configured an encrypted filesystem on my RH9 server following the instructions on QVADIS website:
http://www.q-vadis.net/index.php?mID=stories&lng=en&art=5
today I migrated the serve to Taolinux 1.0 http://www.taolinux.org (it's basically a RHEL rebuild)
and I'm totally screwed :(
I spent a few hours reading newsgroup posts and crypto related informations, tried diffeent falvors and combination of patched on util-linux but unfortunately I wasnt able to sort things up.
---
My last try was using the latest util-linux v2.12 + loop-aes v2.1b:
./losetup -e aes-256 -H rmd160 /dev/loop0 /glcrypto Password:
WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING
Passwords shorter than 20 characters are considered too short and insecure. Use of rmd160 password hash permits use of such short passwords for compatibility with other systems that do not enforce minimum length. Hopefully this message is annoying enough that you discontinue using such short passwords.
WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING
ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (256 bits) not supported by kernel
---
/proc/crypto shows that my current aes module doesnt support 256bit keysize :(
name : deflate module : kernel
name : aes module : aes blocksize : 16 min keysize : 16 max keysize : 32
---
I'm quite lost, considering on this box I would like to stay with stock/not hand-patched RH/TAO kernels instead of building my own.
---
dmesg show that the kernel has CryptoAPI support:
[root@ns2 cipher-aes-i586-0.3]# dmesg | grep Cry Initializing Cryptographic API
---
compiling cipher-aes-i586-0.3 didnt help :(
[root@ns2 cipher-aes-i586-0.3]# insmod ./cipher-aes.o ./cipher-aes.o: unresolved symbol unregister_cipher ./cipher-aes.o: unresolved symbol register_cipher [root@ns2 cipher-aes-i586-0.3]# depmod ./cipher-aes.o depmod: *** Unresolved symbols in ./cipher-aes.o ./cipher-aes.o:
# module id=string
# pci module vendor device subvendor subdevice class class_mask driver_data
# isapnp module cardvendor carddevice driver_data vendor function ...
# usb module match_flags idVendor idProduct bcdDevice_lo bcdDevice_hi bDeviceClass bDeviceSubClass bDeviceProtocol bInterfaceClass bInterfaceSubClass bInterfaceProtocol driver_info
# module pattern
# ieee1394 module match_flags vendor_id model_id specifier_id version
# module id
---
I'm running stock kernel 2.4.21-15.0.3.TL
---
Thanx a lot in advance for your time guys, I hope someone could help me sort this up :)
Best,
nettie
- Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
