From: Eric Biggers <ebiggers@kernel.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Ard Biesheuvel <ardb@kernel.org>, linux-crypto@vger.kernel.org
Subject: Re: Adding algorithm agility to the crypto library functions
Date: Tue, 14 Oct 2025 17:39:47 +0000 [thread overview]
Message-ID: <20251014173947.GA2923951@google.com> (raw)
In-Reply-To: <607ba12f2700e4a5bca9e403dd4c215d7cb6e078.camel@HansenPartnership.com>
On Tue, Oct 14, 2025 at 01:32:01PM -0400, James Bottomley wrote:
> NIST is deprecating sha-256 for Post Quantum so it's a time limited
> choice before we have to do agile anyway.
So support SHA-256 and SHA-512.
Let's not do "we have to support multiple algorithms anyway, so let's
add a bunch of other random algorithms too".
- Eric
next prev parent reply other threads:[~2025-10-14 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 16:01 Adding algorithm agility to the crypto library functions James Bottomley
2025-10-14 16:55 ` Eric Biggers
2025-10-14 17:08 ` Ard Biesheuvel
2025-10-14 17:30 ` Eric Biggers
2025-10-14 17:32 ` James Bottomley
2025-10-14 17:39 ` Eric Biggers [this message]
2025-10-14 20:17 ` James Bottomley
2025-10-15 4:59 ` Simon Richter
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=20251014173947.GA2923951@google.com \
--to=ebiggers@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=ardb@kernel.org \
--cc=linux-crypto@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox