From: Eric Biggers <ebiggers@kernel.org>
To: Pascal Van Leeuwen <pvanleeuwen@verimatrix.com>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: generic ahash question
Date: Fri, 19 Jul 2019 09:23:04 -0700 [thread overview]
Message-ID: <20190719162303.GB1422@gmail.com> (raw)
In-Reply-To: <MN2PR20MB297347B80C7E3DCD19127B05CACB0@MN2PR20MB2973.namprd20.prod.outlook.com>
On Fri, Jul 19, 2019 at 02:41:03PM +0000, Pascal Van Leeuwen wrote:
> Hi,
>
> I recall reading somewhere in the Linux Crypto documentation that support for finup() and digest()
> calls were explicitly added to support hardware that couldn't handle seperate init/update/final
> calls so they could at least be used with e.g. the IPsec stack. I also noticed that testmgr *does*
> attempt to verify these seperate calls ...
>
> So I'm guessing there must be some flags that I can set to indicate I'm not supporting seperate
> init/update/final calls so that testmgr skips those specific tests? Which flag(s) do I need to set?
>
Where does the documentation say that?
AFAICS, init/update/final have been mandatory for at least 9 years, as that's
when testmgr started testing it. See:
commit a8f1a05292db8b410be47fa905669672011f0343
Author: David S. Miller <davem@davemloft.net>
Date: Wed May 19 14:12:03 2010 +1000
crypto: testmgr - Add testing for async hashing and update/final
- Eric
next prev parent reply other threads:[~2019-07-19 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 14:41 generic ahash question Pascal Van Leeuwen
2019-07-19 14:58 ` Herbert Xu
2019-07-19 16:02 ` Pascal Van Leeuwen
2019-07-19 16:23 ` Eric Biggers [this message]
2019-07-19 19:33 ` Pascal Van Leeuwen
2019-07-19 20:07 ` Eric Biggers
2019-07-19 21:30 ` Pascal Van Leeuwen
2019-07-20 2:50 ` 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=20190719162303.GB1422@gmail.com \
--to=ebiggers@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=pvanleeuwen@verimatrix.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.