From: Markus Huehnerbein <silencer@gmx.ch>
To: Sebastian Siewior <linux-crypto@ml.breakpoint.cc>
Cc: linux-crypto@vger.kernel.org
Subject: Re: Problem using dm-crypt with geode LX800 AES-Engine
Date: Wed, 29 Aug 2007 16:41:57 +0200 [thread overview]
Message-ID: <46D585B5.9090607@gmx.ch> (raw)
In-Reply-To: <20070829141549.GD24782@Chamillionaire.breakpoint.cc>
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 algorithm in the cryptoAPI?
Thanks,
Markus
Sebastian Siewior wrote:
> * 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 successfully. The
>> problem is, that if the module is loaded and I try:
>> cryptsetup -c aes -s 256 -h sha256 luksFormat /dev/hda2
>
>>from a quick look into the source it should work with '-s 128' or
> without the -s parameter. Can you confirm this?
>
> Sebastian
> -
> To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2007-08-29 14:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 13:50 Problem using dm-crypt with geode LX800 AES-Engine Markus Huehnerbein
2007-08-29 14:15 ` Sebastian Siewior
2007-08-29 14:41 ` Markus Huehnerbein [this message]
2007-08-29 16:22 ` Sebastian Siewior
2007-08-29 20:29 ` Markus Huehnerbein
2007-08-30 9:01 ` Sebastian Siewior
2007-08-30 18:25 ` Markus Huehnerbein
2007-08-31 1:28 ` Herbert Xu
2007-08-31 12:40 ` Markus Huehnerbein
2007-08-31 14:55 ` Herbert Xu
2007-08-31 17:20 ` Markus Huehnerbein
2007-08-31 18:14 ` Sebastian Siewior
2007-08-31 20:39 ` Sebastian Siewior
2007-08-29 23:55 ` Herbert Xu
2007-08-30 0:07 ` Jordan Crouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46D585B5.9090607@gmx.ch \
--to=silencer@gmx.ch \
--cc=linux-crypto@ml.breakpoint.cc \
--cc=linux-crypto@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).