From: <Dmitry.Kasatkin@nokia.com>
To: <herbert@gondor.hengli.com.au>
Cc: <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH 0/2] crypto: omap-sha1-md5: OMAP3 SHA1 & MD5 driver
Date: Thu, 8 Apr 2010 18:35:33 +0200 [thread overview]
Message-ID: <1270744533.1666.9.camel@Nokia-N900> (raw)
----- Original message -----
> Hi:
>
> OK so you did answer my question :)
>
> Dmitry Kasatkin <dmitry.kasatkin@nokia.com> wrote:
> >
> > Interesting case with hmac.
> >
> > return crypto_shash_init(&desc.shash) ?:
> > crypto_shash_update(&desc.shash, ipad, bs) ?:
> > crypto_shash_export(&desc.shash, ipad) ?:
> > crypto_shash_init(&desc.shash) ?:
> > crypto_shash_update(&desc.shash, opad, bs) ?:
> > crypto_shash_export(&desc.shash, opad);
> >
> > Basically it does not call final.
> > Then call init again.
> >
> > hw has certain limitation that it requires to process last block with
> > some bit set.
> > WHen update is called there is no possibility to know that no more
> > update() will come.
> > So possible last block is stored and then hashed out from the final.
> >
> > I see that above code will not work with the driver.
> > I wonder how intermediate export/import could be done with omap hw.
> >
> > But if it's not possible, then why not to have hmac(sha1) as just sw.
> > Anyway hmac should not process as huge amount of data as hash itself.
> >
> > What is your opinion/advice?
>
> A sha1-only driver is not very useful since the biggest potential
> user IPsec uses hmac(sha1).
>
> Is the omap hw documentation available publicly?
>
> Thanks,
> --
> Visit Openswan at http://www.openswan.org/
> Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
> --
> 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
>
Hi.
Sha1 only is also very useful. We calcluate hashes of all binaries for integrity verification. We do not need hmac there.
But in general it is possible do add algo hmac(sha1) to the driver and implement it internally without import/export.
I have to check on documentation publicity.
Br,
Dmitry
next reply other threads:[~2010-04-08 16:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 16:35 Dmitry.Kasatkin [this message]
2010-04-13 8:59 ` [PATCH 0/2] crypto: omap-sha1-md5: OMAP3 SHA1 & MD5 driver Herbert Xu
2010-04-13 9:39 ` Dmitry Kasatkin
2010-04-13 10:03 ` Herbert Xu
2010-04-13 10:13 ` Dmitry Kasatkin
2010-04-13 12:02 ` Herbert Xu
2010-04-13 13:00 ` Dmitry Kasatkin
2010-04-13 14:45 ` Herbert Xu
2010-04-13 15:16 ` Uri Simchoni
2010-04-13 15:21 ` Dmitry Kasatkin
2010-04-14 0:44 ` Herbert Xu
2010-04-14 6:37 ` Dmitry Kasatkin
2010-04-14 6:44 ` Herbert Xu
2010-04-14 6:51 ` Dmitry Kasatkin
2010-04-14 6:55 ` Herbert Xu
2010-04-16 7:44 ` Dmitry Kasatkin
2010-04-19 13:27 ` Herbert Xu
2010-04-13 10:15 ` Dmitry Kasatkin
2010-04-13 12:00 ` Uri Simchoni
2010-04-13 12:10 ` Herbert Xu
2010-04-13 13:44 ` Dmitry Kasatkin
2010-04-13 14:36 ` Dmitry Kasatkin
2010-04-13 14:42 ` Herbert Xu
2010-04-13 15:33 ` Dmitry Kasatkin
2010-04-14 0:47 ` Herbert Xu
2010-04-13 14:48 ` Herbert Xu
2010-04-13 15:48 ` Dmitry Kasatkin
2010-04-14 0:50 ` Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2010-03-17 13:12 Dmitry Kasatkin
2010-03-23 11:32 ` Herbert Xu
2010-03-24 7:31 ` Dmitry Kasatkin
2010-03-24 14:51 ` Dmitry Kasatkin
2010-04-08 14:07 ` Herbert Xu
2010-04-08 14:04 ` 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=1270744533.1666.9.camel@Nokia-N900 \
--to=dmitry.kasatkin@nokia.com \
--cc=herbert@gondor.hengli.com.au \
--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;
as well as URLs for NNTP newsgroup(s).