Re: Problem using dm-crypt with geode LX800 AES-Engine

* Markus Huehnerbein | 2007-08-29 22:29:10 [+0200]:

Yes, again you're right, if I use a hash with 256 bit I get the
following syslog errors:

device-mapper: table: 254:1: crypt: Error initializing ESSIV hash

This error message should only come up if dm was not able to allocate
the hash in kernel so may miss SHA256 support.

device-mapper: ioctl: error adding target to table
device-mapper: ioctl: device doesn't appear to be in the dev hash table.

Unfortunately there is no support for sha128 in the Kernel so I tried

well there is no sha128. I was probabaly thinking of sha1 but that one
generates 160 bit long signatures.

md5 as md5 also generates a 128 bit value.

Preparing the Volume with:
cryptsetup -c aes-cbc-essiv:md5 -y -s 128 luksFormat /dev/hda2
works fine ("Command successful" and no errors in the syslog) but when I
try to open the device
cryptsetup luksOpen /dev/hda2 devdmcryptluks
I get "Command failed." after entering the (correct) password. I also
tried "luksOpen" with the same arguments as "luksFormat" but the same -
"Command failed." without any trace in the syslog...

That should have work. Does it work with the generic aes driver instead
of geode?

Markus

Sebastian