linux-kernel - Re: how to verify which crypto driver is loaded by crypto_alloc_shash when more than one available for the algorithm

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-prev] [day] [month] [year] [list]

Date: Thu, 20 Jun 2024 08:41:36 +0200
From: Ard Biesheuvel <ardb@...nel.org>
To: Steve French <smfrench@...il.com>
Cc: "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" <linux-crypto@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: how to verify which crypto driver is loaded by crypto_alloc_shash
 when more than one available for the algorithm

On Thu, 20 Jun 2024 at 00:03, Steve French <smfrench@...il.com> wrote:
>
> Was trying to see which driver was loaded by:
>
>    crypto_alloc_shash(hmac(md5), ...);
>
> and it was confusing because it looked like there were at least five
> drivers that export that cra_name (most presumably hardware specific),
> so was wondering what is the "default" that would be chosen and how to
> tell which of the five ended up being used.
>

You could check the cra_driver_name of the shash's underlying crypto_alg

crypto_alloc_shash(hmac(md5), ...)->base.alg->cra_driver_name