* Sebastian Siewior | 2007-08-31 20:14:32 [+0200]:
>* Markus Huehnerbein | 2007-08-31 14:40:48 [+0200]:
>
>>> Sounds like geode_aes is just broken. Can you please check if
>>> tcrypt with mode=10 and mode=200 work or not with the geode_aes
>>> driver?
>>
>>Below are the syslog entries generated b
* Markus Huehnerbein | 2007-08-31 14:40:48 [+0200]:
>> Sounds like geode_aes is just broken. Can you please check if
>> tcrypt with mode=10 and mode=200 work or not with the geode_aes
>> driver?
>
>Below are the syslog entries generated by modprobe tcrypt mode=10 and
>modprobe tcrypt mode=200 but
> OK. Could you please write 4K zeros to the device with dd and
> then read them back out using od -x?
Hope I did it right:
dd if=/dev/zero of=/dev/mapper/devdmcrypt bs=4k count=1
1+0 records in
1+0 records out
4096 bytes (4.1 kB) copied, 0.0353821 seconds, 116 kB/s
od -x /dev/mapper/devdmcrypt
On Fri, Aug 31, 2007 at 02:40:48PM +0200, Markus Huehnerbein wrote:
>
> Below are the syslog entries generated by modprobe tcrypt mode=10 and
OK. Could you please write 4K zeros to the device with dd and
then read them back out using od -x?
Thanks,
--
Visit Openswan at http://www.openswan.org/
Herbert Xu wrote:
> Markus Huehnerbein <[EMAIL PROTECTED]> wrote:
>> I thought that the problem is maybe related with the use of LUKS / the
>> Master-Key created by the PBKDF2, so I tried cryptsetup without LUKS as
>> follows (with the "geode_aes" module loaded):
>>cryptsetup -y -c aes -h m
Markus Huehnerbein <[EMAIL PROTECTED]> wrote:
>
> I thought that the problem is maybe related with the use of LUKS / the
> Master-Key created by the PBKDF2, so I tried cryptsetup without LUKS as
> follows (with the "geode_aes" module loaded):
>cryptsetup -y -c aes -h md5 -s 128 create devd
>> 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.
By the output of lsmod the sha256 module is loaded. But anyway, I think
in order to benefit from the geode th
* 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 kern
On 30/08/07 07:55 +0800, Herbert Xu wrote:
> Sebastian Siewior <[EMAIL PROTECTED]> wrote:
> >
> > Actually it is. geode does not support keys != 128 bit. ESSIV uses as
> > key the output of sha256 what is 256. Check dmesg please. If my theory
> > is correct than you should see in dmesg or somewher
Sebastian Siewior <[EMAIL PROTECTED]> wrote:
>
> Actually it is. geode does not support keys != 128 bit. ESSIV uses as
> key the output of sha256 what is 256. Check dmesg please. If my theory
> is correct than you should see in dmesg or somewhere:
> "Failed to set key for ESSIV cipher"
> Is it?
J
Sebastian Siewior wrote:
> * Markus Huehnerbein | 2007-08-29 16:41:57 [+0200]:
>
>> Thanks a lot! I confirm that it works with "-s 128" and also if "-s" is
>> skipped! But if I try to use cryptsetup with ESSIV (cryptsetup -c
>> aes-cbc-essiv:sha256 -y -s 128 luksFormat /dev/hda2) I get the same
>
* Markus Huehnerbein | 2007-08-29 16:41:57 [+0200]:
>Thanks a lot! I confirm that it works with "-s 128" and also if "-s" is
>skipped! But if I try to use cryptsetup with ESSIV (cryptsetup -c
>aes-cbc-essiv:sha256 -y -s 128 luksFormat /dev/hda2) I get the same
what about sha128 instead?
>error. I
Thanks a lot! I confirm that it works with "-s 128" and also if "-s" is
skipped! But if I try to use cryptsetup with ESSIV (cryptsetup -c
aes-cbc-essiv:sha256 -y -s 128 luksFormat /dev/hda2) I get the same
error. If the "geode-aes" does not support essiv why is this task not
performed by another al
* Markus Huehnerbein | 2007-08-29 15:50:35 [+0200]:
>I 've an embedded board with AMD Geode??? LX 800 Chip. I'm running Debian
>Etch and Kernel 2.6.22.5. What I tried is to use dm-crypt /
>cryptsetup-luks 1.0.5 with the Geode AES-Engine.
>
>The Kernel Modul "geode_aes" is compiled and loaded succe
Hello list,
I 've an embedded board with AMD Geode™ LX 800 Chip. I'm running Debian
Etch and Kernel 2.6.22.5. What I tried is to use dm-crypt /
cryptsetup-luks 1.0.5 with the Geode AES-Engine.
The Kernel Modul "geode_aes" is compiled and loaded successfully. The
problem is, that if the module is
15 matches
Mail list logo
