Hm, yes, it seems to be there. On the other hand 2.6.9 is a really, really old kernel and the kernel crypto interface may just have been a bit different back in 2004 when it was current. The would explain the problem. Arno On Wed, Nov 12, 2008 at 11:29:04AM +0800, ?????? wrote: > Thanks Arno! > > But it seems not the reason that causes the problem. > I looked at the output of "cat /proc/crypto", it shows these: > > name : sha1 > module : kernel > type : digest > blocksize : 64 > digestsize : 20 > > name : md5 > module : md5 > type : digest > blocksize : 64 > digestsize : 16 > > name : crc32c > module : crc32c > type : digest > blocksize : 32 > digestsize : 4 > > name : aes > module : aes > type : cipher > blocksize : 16 > min keysize : 16 > max keysize : 32 > > I have tried sha1, it reports the same error. I think the modules needed have been loaded. So, what is the reason that causes the error? > > > Besides, I am using CentOS 4.6 and am trying to setup an encrypted logical volume on an existing normal logical volume. > Here are some information about my system: > # uname -a > Linux xxx.xxx.com 2.6.9-67.ELsmp #1 SMP Fri Nov 16 12:49:06 EST 2007 x86_64 x86_64 x86_64 GNU/Linux > > Any other information may help? > > Mersenne Yang > > On Tue, Nov 11, 2008 at 04:40:30PM +0800, ?????? wrote: > > Hi, all, > > > > When I tried to create an encrypt volume, I encounter an error as follows: > > > > # ./cryptsetup create --cipher=aes --hash=md5 aaa /dev/myvg/lvol0 > > Enter passphrase: > > Command failed: Key processing error: No hash backend found > > I suspect that means missing md5 support in the kernel. Have > a look at the output of "cat /proc/crypto" (may be long, > you may want to pipe it into less or a file). The md5 entry looks > something like this: > > name : md5 > driver : md5-generic > module : kernel > priority : 0 > refcnt : 1 > type : digest > blocksize : 64 > digestsize : 16 > > > > And if I try this: > > # ./cryptsetup create --cipher=aes --hash=plain aaa /dev/myvg/lvol0 > > > > It works but alert another error. > > sh: /sbin/udevsettle: No such file or directory > > This seems to indicate a problem with /dev/myvg/lvol0, > which is probably generated by udev. Maybe the udev > installation is broken or the version is too new/old? > Sorry, I do not really understand udev at this time. > > > Did I have missed any lib file or wrongly configured any thing? > > If this is a monolitic kernel you may have to compile > md5 support into the kernel. If it is a module kernel, > you may just have to load the md5 module (if present). > > Arno > > -- > Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@xxxxxxxxxxx > GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F > ---- > Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans > > If it's in the news, don't worry about it. The very definition of > "news" is "something that hardly ever happens." -- Bruce Schneier > > --------------------------------------------------------------------- > dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ > To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx > For additional commands, e-mail: dm-crypt-help@xxxxxxxx > > > > Powered by MessageSoft SMG > SPAM, virus-free and secure email > > > > Powered by MessageSoft SMG > SPAM, virus-free and secure email > > > --------------------------------------------------------------------- > dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ > To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx > For additional commands, e-mail: dm-crypt-help@xxxxxxxx > -- Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@xxxxxxxxxxx GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F ---- Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans If it's in the news, don't worry about it. The very definition of "news" is "something that hardly ever happens." -- Bruce Schneier --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
