All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jordan Crouse" <jordan.crouse@amd.com>
To: "Herbert Xu" <herbert@gondor.apana.org.au>
Cc: linux-crypto@ml.breakpoint.cc, silencer@gmx.ch,
	linux-crypto@vger.kernel.org
Subject: Re: Problem using dm-crypt with geode LX800 AES-Engine
Date: Wed, 29 Aug 2007 18:07:54 -0600	[thread overview]
Message-ID: <20070830000754.GD5851@cosmic.amd.com> (raw)
In-Reply-To: <E1IQXNV-0003Ed-00@gondolin.me.apana.org.au>

On 30/08/07 07:55 +0800, Herbert Xu wrote:
> Sebastian Siewior <linux-crypto@ml.breakpoint.cc> 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?
> 
> Jordan, could you please confirm whether geode-aes supports
> key sizes other than 128, i.e., 192 and 256?

No  - just 128.  Bad planning, I guess... :)

JOrdan

-- 
Jordan Crouse
Systems Software Development Engineer 
Advanced Micro Devices, Inc.

      reply	other threads:[~2007-08-30  0:07 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
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 [this message]

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=20070830000754.GD5851@cosmic.amd.com \
    --to=jordan.crouse@amd.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@ml.breakpoint.cc \
    --cc=linux-crypto@vger.kernel.org \
    --cc=silencer@gmx.ch \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.