From: Eric Biggers <ebiggers@kernel.org>
To: Ryan Appel <ryan.appel.333@gmail.com>
Cc: linux-crypto@vger.kernel.org, wireguard@lists.zx2c4.com,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: Re: Kernel ML-KEM implementation plans
Date: Mon, 30 Mar 2026 17:13:58 -0700 [thread overview]
Message-ID: <20260331001358.GA5190@sol> (raw)
In-Reply-To: <5F9ACD7A-F3B8-463A-A00E-28F68819A66C@gmail.com>
On Mon, Mar 30, 2026 at 06:41:46PM -0500, Ryan Appel wrote:
> Hello all,
>
> Looking through the mail archives I see no information on an
> implementation of ML-KEM that has been planned, except for leancrypto
> attempting to make a Key-Agreement Scheme a Key-Encapsulation
> Mechanism.
>
> Is there a plan to implement a KEM interface at this point? Is this
> something that needs support? How could someone contribute to this?
We don't add new algorithms preemptively, but rather only when an
in-kernel user comes along. Otherwise there's a risk that the code will
never be used.
Do you have a specific in-kernel user in mind? I haven't actually heard
anyone specifically say they need ML-KEM in the kernel yet.
I guess the obvious use case would be WireGuard. But that would require
a new WireGuard protocol version that replaces X25519 with something
like X25519MLKEM768. It's going to be up to the WireGuard author
(Jason) to decide whether that's in the roadmap for WireGuard.
Also maybe Bluetooth, though it seems the spec for that is yet to be
defined?
Anyway, point is, before it makes sense to consider possible
implementation strategies, there needs to be a plan to actually use it.
- Eric
next prev parent reply other threads:[~2026-03-31 0:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 23:41 Kernel ML-KEM implementation plans Ryan Appel
2026-03-31 0:13 ` Eric Biggers [this message]
2026-03-31 0:44 ` Ryan Appel
2026-03-31 1:11 ` Eric Biggers
2026-04-02 17:08 ` Ryan Appel
2026-04-06 18:27 ` Chris Leech
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=20260331001358.GA5190@sol \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=linux-crypto@vger.kernel.org \
--cc=ryan.appel.333@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/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