From: Adrian-Ken Rueegsegger <ken@codelabs.ch>
To: herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org, steffen.klassert@secunet.com
Subject: [PATCH 0/4] Switch remaining algorithms to shash
Date: Thu, 4 Dec 2008 01:18:08 +0100 [thread overview]
Message-ID: <12283498922490-git-send-email-ken@codelabs.ch> (raw)
This series converts the remaining hash algorithms to use the new shash
interface.
The first patch removes the message schedule W from struct sha512_ctx
since it gets calculated anew on each execution of sha512_transform. This
reduces the size of sha512_ctx considerably and will allow it to be
registered as a shash algorithm (it will pass the size check in
crypto_register_shash (crypto/shash.c:490)).
Herbert, could you explain why descsize must be smaller (or equal)
than PAGE_SIZE / 8?
The next two patches switch sha512 and wp512 to the new shash interface.
The fourth patch is another try to convert michael_mic. The key values
l and r are duplicated in the descriptor part since they are used and
changed during the actual transformation. I would be gratefull for
comments on this patch since I am not sure it's the proper way to do it.
Adrian
next reply other threads:[~2008-12-04 0:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 0:18 Adrian-Ken Rueegsegger [this message]
2008-12-04 0:18 ` [PATCH 1/4] crypto: sha512 - Remove W (message schedule) from struct sha512_ctx Adrian-Ken Rueegsegger
2008-12-04 0:18 ` [PATCH 2/4] crypto: sha512 - Switch to shash Adrian-Ken Rueegsegger
2008-12-04 0:18 ` [PATCH 3/4] crypto: wp512 " Adrian-Ken Rueegsegger
2008-12-04 0:18 ` [PATCH 4/4][RFC] crypto: michael_mic " Adrian-Ken Rueegsegger
2008-12-04 3:29 ` Herbert Xu
2008-12-04 8:04 ` Adrian-Ken Rueegsegger
2008-12-04 6:48 ` [PATCH 0/4] Switch remaining algorithms " Herbert Xu
2008-12-04 7:55 ` Adrian-Ken Rueegsegger
2008-12-04 8:02 ` Herbert Xu
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=12283498922490-git-send-email-ken@codelabs.ch \
--to=ken@codelabs.ch \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/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.