From: Eric Biggers <ebiggers@kernel.org>
To: "Rusydi H. Makarim" <rusydi.makarim@kriptograf.id>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Ard Biesheuvel <ardb@kernel.org>,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH 0/3] Implementation of Ascon-Hash256
Date: Mon, 15 Dec 2025 20:19:32 +0000 [thread overview]
Message-ID: <20251215201932.GC10539@google.com> (raw)
In-Reply-To: <20251215-ascon_hash256-v1-0-24ae735e571e@kriptograf.id>
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@kriptograf.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
next prev parent reply other threads:[~2025-12-15 20:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 7:54 [PATCH 0/3] Implementation of Ascon-Hash256 Rusydi H. Makarim
2025-12-15 7:54 ` [PATCH 1/3] lib/crypto: Add KUnit test vectors for Ascon-Hash256 Rusydi H. Makarim
2025-12-19 4:29 ` kernel test robot
2025-12-22 17:11 ` kernel test robot
2025-12-15 7:54 ` [PATCH 2/3] lib/crypto: Initial implementation of Ascon-Hash256 Rusydi H. Makarim
2025-12-15 23:01 ` kernel test robot
2025-12-20 15:34 ` kernel test robot
2025-12-20 16:20 ` kernel test robot
2025-12-22 17:41 ` kernel test robot
2025-12-15 7:54 ` [PATCH 3/3] crypto: Crypto API " Rusydi H. Makarim
2025-12-15 20:19 ` Eric Biggers [this message]
2025-12-16 6:27 ` [PATCH 0/3] Implementation " Rusydi H. Makarim
2025-12-16 18:02 ` Eric Biggers
[not found] ` <bb05699bc7922bb3668082367b4750f2@kriptograf.id>
2025-12-17 4:06 ` Eric Biggers
2025-12-31 9:20 ` Rusydi H. Makarim
2026-01-01 21:06 ` Eric Biggers
2026-01-01 23:35 ` David Laight
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251215201932.GC10539@google.com \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusydi.makarim@kriptograf.id \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.