linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <CAH2r5mterW6Qqyz=oirYr1iV5jLRAvfU5yGGd2MOqpkwaE0qhQ@mail.gmail.com>
Date: Wed, 19 Jun 2024 17:03:17 -0500
From: Steve French <smfrench@...il.com>
To: "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" <linux-crypto@...r.kernel.org>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: how to verify which crypto driver is loaded by crypto_alloc_shash
 when more than one available for the algorithm

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.

-- 
Thanks,

Steve