From: Michal Ludvig <michal@logix.cz>
To: Sebastian Siewior <linux-crypto@ml.breakpoint.cc>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [patch 0/2] remove setkey function in VIA's padlock
Date: Mon, 05 Nov 2007 12:54:50 +1300 [thread overview]
Message-ID: <472E5BCA.2060000@logix.cz> (raw)
In-Reply-To: <20071102181323.632030242@ml.breakpoint.cc>
Sebastian Siewior wrote:
> Hello Michal,
>
> you wrote the padlock-aes driver so you probably have the hardware for
> testing :) The setkey function in the driver's code looks like it
> expands the key the same way like the new crypto_aes_set_key() I've
> posted earlier [1], [2]. Could you please test this patch and see if it is
> working correct?
I'll test and get back to you.
> I have one question regarding the size of the expanded key: You reserve
> 64 * 4 bytes for each key but it seems that you use only 60 * 4 bytes.
> Are the other bytes used by the hardware or did you allocate it by
> accident?
The hardware needs it. From the VIA Padlock Programming Guide:
| For the application-loaded keys option, the hardware always
| loads sixteen 128-bit values from memory regardless of the
| specified key size. Any values beyond the normal extended key
| size are ignored and have no effect on the results, but that
| memory area must be accessible (within the segment limit, etc.)
Michal
--
* http://www.logix.cz/michal
next parent reply other threads:[~2007-11-05 0:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071102181323.632030242@ml.breakpoint.cc>
2007-11-04 23:54 ` Michal Ludvig [this message]
2007-11-10 21:23 ` [patch 0/2] remove setkey function in VIA's padlock Sebastian Siewior
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=472E5BCA.2060000@logix.cz \
--to=michal@logix.cz \
--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 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.