From: Stefan Hellermann <stefan@the2masters.de>
To: Sebastian Siewior <sebastian@breakpoint.cc>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [RFC] padlock aes, unification of setkey()
Date: Sun, 24 Feb 2008 12:54:20 +0100 [thread overview]
Message-ID: <47C15AEC.5040705@the2masters.de> (raw)
In-Reply-To: <1203850864-16681-1-git-send-email-sebastian@breakpoint.cc>
Hello,
I'm got my Via Epia SN Board a few days ago and could test everything related to the
padlock engine, I'm especially interested in the aes-{lrw,xts} combo, this doesn't work at
the moment (last tested with 2.6.25-rc1).
Cheers,
Stefan
Sebastian Siewior schrieb:
> From Sebastian Siewior <sebastian@breakpoint.cc> # This line is ignored.
> Subject: [RFC] padlock aes, unification of setkey()
>
> Hello Herbert,
>
> I sit on those two since November. Back then Michal dropped me an email
> and told me that he will test it and get back to me. This didn't happen
> so far.
> The binary format of the key was the same, the last time I checked, so
> the second patch could really work :)
>
> One thing I'm concerned about is the stack utilization. The initial
> version had a structure with 256 bytes on the stack. Mine has a bigger
> structure with 484 bytes. I'm not sure if it is better to dynamically
> allocate it, move it to the private key structure or pad the generic
> aes structure in order to enforce the required alignment.
>
> 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:[~2008-02-24 12:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 11:01 [RFC] padlock aes, unification of setkey() Sebastian Siewior
2008-02-24 11:01 ` [RFC] generic_aes: export generic setkey Sebastian Siewior
2008-03-13 21:40 ` Stefan Hellermann
2008-02-24 11:01 ` [RFC] [crypto] padlock-AES, use generic setkey function Sebastian Siewior
2008-03-13 21:40 ` Stefan Hellermann
2008-03-14 11:44 ` Sebastian Siewior
2008-03-14 12:49 ` Stefan Hellermann
2008-03-14 14:16 ` Sebastian Siewior
2008-04-01 13:25 ` Herbert Xu
2008-02-24 11:54 ` Stefan Hellermann [this message]
2008-02-24 12:51 ` [RFC] padlock aes, unification of setkey() Sebastian Siewior
2008-02-24 20:07 ` Via Padlock Bug with LRW/XTS Stefan Hellermann
2008-02-27 8:30 ` Sebastian Siewior
2008-03-02 11:20 ` [PATCH] [crypto] XTS: use proper alignment Sebastian Siewior
2008-03-02 12:04 ` Stefan Hellermann
2008-03-02 13:22 ` Sebastian Siewior
2008-03-02 13:49 ` Stefan Hellermann
2008-03-02 14:04 ` Stefan Hellermann
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=47C15AEC.5040705@the2masters.de \
--to=stefan@the2masters.de \
--cc=linux-crypto@vger.kernel.org \
--cc=sebastian@breakpoint.cc \
/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.