I was mistaken when using SHA1. But for example AES does not work. It is possible to ask to give an example precisely working? About 2 years ago problems has not arisen. # losetup -e AES /dev/loop0 /tmp/cr Password: ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (128 bits) not supported by kernel # losetup -e AES128 /dev/loop0 /tmp/cr Password: ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (128 bits) not supported by kernel Solar Designer пишет: > On Tue, Jun 13, 2006 at 04:00:08PM +0400, Maxim Timofeyev wrote: >> For some reason it is impossible to create crypto fs... >> >> # for i in aes anubis arc4 blowfish cast5 cast6 crypto_null deflate des khazad >> md4 md5 michael_mic serpent sha1 sha256 sha512 tcrypt tea twofish wp512; do >> modprobe $i; done >> >> # echo 123 | losetup -e sha1 -k 128 -p 0 /dev/loop0 /dev/md4 >> ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (128 >> bits) not supported by kernel > > You're doing something weird. SHA-1 is a message digest (hashing) > algorithm, you can't use it as the cipher for encrypting a filesystem. > > Also, most of the time you should not be specifying an explicit key size > (the -k option). Once you choose a cipher, there are only a few or even > a single valid key size for that cipher. If you try to specify another > (invalid) key size, you will get an error message such as the above. > -- С уважением, Тимофеев Максим Анатольевич JabberID: tma@private E-Mail: tma@private WWW: http://tma.spb.ru
This archive was generated by hypermail 2.1.3 : Thu Jun 15 2006 - 07:48:45 PDT