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: Thu, 30 Aug 2007 20:25:53 +0200 [thread overview]
Message-ID: <46D70BB1.907@gmx.ch> (raw)
In-Reply-To: <20070830090128.GA29936@Chamillionaire.breakpoint.cc>
>> 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 the only way is to use md5, as there
is no other digest that provides a 128-bit value - execpt maybe tiger.
>>
>> 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?
Yes, with the generic driver luksFormat as well as luksOpen works fine.
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 devdmcrypt /dev/hda2
-No errors, neither in syslog nor in the output
-Checking the output of "dmsetup ls":
devdmcrypt (254, 0)
-Creating ext2 filesystem
mkfs.ext2 /dev/mapper/devdmcrypt
-Trying to mount /dev/mapper/devdmcrypt fails with "wrong fs type..."
and syslog error: "VFS: Can't find an ext2 filesystem on dev dm-0"
I'm not sure whether the problems are linked to each other or not but
maybe it could be of interesst.
--Markus
next prev parent reply other threads:[~2007-08-30 18:25 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
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 [this message]
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=46D70BB1.907@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).