[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251215201932.GC10539@google.com>
Date: Mon, 15 Dec 2025 20:19:32 +0000
From: Eric Biggers <ebiggers@...nel.org>
To: "Rusydi H. Makarim" <rusydi.makarim@...ptograf.id>
Cc: Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>,
"Jason A. Donenfeld" <Jason@...c4.com>,
Ard Biesheuvel <ardb@...nel.org>, linux-kernel@...r.kernel.org,
linux-crypto@...r.kernel.org
Subject: Re: [PATCH 0/3] Implementation of Ascon-Hash256
On Mon, Dec 15, 2025 at 02:54:33PM +0700, Rusydi H. Makarim wrote:
> This patch implements Ascon-Hash256. Ascon-Hash256 is a hash function as a part
> of the Ascon-Based Lightweight Cryptography Standards for Constrained Devices,
> published as NIST SP 800-232 (https://csrc.nist.gov/pubs/sp/800/232/final).
>
> Signed-off-by: Rusydi H. Makarim <rusydi.makarim@...ptograf.id>
What is the use case for supporting this algorithm in the kernel? Which
specific kernel subsystem will be using this algorithm, and why?
There's a significant maintainence cost to each supported algorithm. So
if there's no in-kernel user, there's no need to add this.
- Eric
Powered by blists - more mailing lists