linux-kernel - Re: [GIT PULL] Crypto Update for 6.15

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

Message-ID: <CAHk-=wi5Ebhdt=au6ymV--B24Vt95Y3hhBUG941SAZ-bQB7-zA@mail.gmail.com>
Date: Sat, 29 Mar 2025 11:17:17 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Eric Biggers <ebiggers@...nel.org>
Cc: Herbert Xu <herbert@...dor.apana.org.au>, "David S. Miller" <davem@...emloft.net>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, 
	Linux Crypto Mailing List <linux-crypto@...r.kernel.org>
Subject: Re: [GIT PULL] Crypto Update for 6.15

On Sat, 29 Mar 2025 at 11:06, Eric Biggers <ebiggers@...nel.org> wrote:
>
> The crypto_shash API is synchronous and operates on virtual addresses.  So it
> just provides a simple way to support multiple hash algorithms, and none of the
> legacy asynchronous hardware offload stuff.  It's crypto_ahash that has that.

Well, it's "simple" only compared to ahash.

It's still a complete nightmare compared to just doing the obvious
thing directly when that is an option.

I happened to just merge the rdma updates a couple of minutes ago, and
they actually removed the example I was using (ie the whole "use
crypto layer for crc32c" insanity).

             Linus