From: Emanuele Cesena <emanuele.cesena@gmail.com>
To: linux-crypto@vger.kernel.org
Subject: Status of shash
Date: Tue, 29 Dec 2009 18:00:17 +0100 [thread overview]
Message-ID: <1262106017.2726.27.camel@ec> (raw)
Hi all,
I'd like to better understand the future plans for shash.
Currently I can see that (please correct me if I'm wrong):
- all the hash algorithms are migrated to shash
- most of the kernel code uses the ahash API
- still some pieces are using the hash API (e.g. IMA)
I want to build a module on top of hash tfm API.
What should I use? I guess ahash.
In fact I don't need async, while I'd like export/import functions.
So, can I already use shash?
What about the (near) future? Is it better (for sync) to use hash, or to
wait for shash [*], or to use ahash in any case?
BTW, should IMA be converted to ahash?
This could be a good exercise to start...
Best,
[*] I made some preliminary tests and shash gave me some problems.
Further, looking at the code, it seems it is not yet completely
implemented w.r.t. the tfm API.
--
Emanuele Cesena <emanuele.cesena@gmail.com>
Il corpo non ha ideali
next reply other threads:[~2009-12-29 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 17:00 Emanuele Cesena [this message]
2010-01-12 11:20 ` Status of shash 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=1262106017.2726.27.camel@ec \
--to=emanuele.cesena@gmail.com \
--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