From: Dimitrios Siganos <dimitris@siganos.org>
To: linux-crypto@vger.kernel.org
Subject: hmac(sha1)
Date: Wed, 03 Mar 2010 03:29:17 +0000 [thread overview]
Message-ID: <4B8DD78D.6080707@siganos.org> (raw)
Hi,
I am trying to write a hmac(sha1) algorithm and I have a few questions.
I have a HW crypto accelerator that does the actual crypto work. I have
already successfully implemented sha1 by creating a
CRYPTO_ALG_TYPE_DIGEST algorithm.
1) Can I implement hmac(sha1) as a CRYPTO_ALG_TYPE_DIGEST algorithm
(i.e. use very similar code to sha1)?
2) Do I need to create a CRYPTO_ALG_TYPE_HASH algorithm?
3) Is it possible to implement hmac(sha1) as both CRYPTO_ALG_TYPE_DIGEST
and CRYPTO_ALG_TYPE_HASH?
4) If I use a CRYPTO_ALG_TYPE_HASH, I need to understand the scatterwalk
api, is there any help on the subject?
Regards,
Dimitris
next reply other threads:[~2010-03-03 3:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 3:29 Dimitrios Siganos [this message]
2010-03-03 20:17 ` hmac(sha1) Dimitrios Siganos
2010-03-03 22:59 ` hmac(sha1) Kim Phillips
2010-03-05 7:32 ` hmac(sha1) Herbert Xu
2010-03-05 16:17 ` hmac(sha1) Dimitrios Siganos
2010-03-09 3:08 ` hmac(sha1) Herbert Xu
2010-03-10 2:48 ` hmac(sha1) Dimitrios Siganos
2010-03-10 4:05 ` hmac(sha1) 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=4B8DD78D.6080707@siganos.org \
--to=dimitris@siganos.org \
--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