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 <[email protected]>
Date: Wed May 19 14:12:03 2010 +1000
crypto: testmgr - Add testing for async hashing and update/final
- Eric
