lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <729A4150-93A0-456B-B7AB-6D3A446E600E@sigma-star.at>
Date:   Wed, 29 May 2019 16:04:47 +0200
From:   David Gstir <david@...ma-star.at>
To:     Linux Crypto Mailing List <linux-crypto@...r.kernel.org>
Cc:     linux-kernel@...r.kernel.org, Richard Weinberger <richard@....at>
Subject: Can an ahash driver be used through shash API?

Hi!

I've done some testing with hardware acceleration of hash functions
and noticed that, when using the synchronous message digest API (shash),
some drivers are not usable. In my case the CAAM driver for SHA256.
Using the asynchronous interface (ahash), everything works as expected.
Looking at the driver source, the CAAM driver only implements the ahash
interface. 

I'm wondering if there a way to use an ahash driver through the shash interface?

I've seen that it does actually work the other way around, since 
crypto_init_shash_ops_async() in crypto/shash.c takes care of translating calls
from ahash to shash and that's how the *-generic drivers are usable through the
ahash API.

Thanks!
David

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ