linux-kernel - Re: Pick up keys-pqc branch for linux-next?

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

Message-ID: <20251121024858.GF3078357@google.com>
Date: Fri, 21 Nov 2025 02:48:58 +0000
From: Eric Biggers <ebiggers@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: David Howells <dhowells@...hat.com>, Mark Brown <broonie@...nel.org>,
	Herbert Xu <herbert@...dor.apana.org.au>,
	linux-crypto@...r.kernel.org, keyrings@...r.kernel.org,
	linux-modules@...r.kernel.org, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: Pick up keys-pqc branch for linux-next?

On Thu, Nov 20, 2025 at 08:53:41PM +1100, Stephen Rothwell wrote:
> Hi David,
> 
> On Mon, 17 Nov 2025 09:11:26 -0800 Eric Biggers <ebiggers@...nel.org> wrote:
> >
> > On Mon, Nov 17, 2025 at 03:22:03PM +0000, David Howells wrote:
> > > 
> > > Can you pick up my keys-pqc branch for linux-next please?  It can be found at:
> > > 
> > > 	https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/
> > > 	keys-pqc
> > > 
> > > Note that it's based on Eric Bigger's libcrypto/lbcrypto-next branch which I
> > > believe you already have in order to get SHA-3/SHAKE support.
> > 
> > I don't really see the point yet, since this isn't going to be ready for
> > the next merge window anyway.
> 
> Yeah, if it is not going into the next merge window, then I don't want
> it until after that merge window closes, OK?

Makes sense to me.  David, with
https://lore.kernel.org/r/20251120003653.335863-2-ebiggers@kernel.org
we're getting closer, but it's still too late for 6.19.  We need proper
tests to be added at the same time as the ML-DSA implementation itself.
The higher-level parts such as crypto/asymmetric_keys/ need review too.
Also, lib/crypto/ changes should go through the libcrypto tree.

wycheproof has negative test vectors for ML-DSA edge cases.  We maybe
could borrow those.  Note that ML-DSA keys and signatures are very
large, which results in huge files for the test vectors.  I'd also like
to keep the size down, but we might not have much choice there.

I'm also working to get another crypto-oriented developer, who doesn't
normally work on the Linux kernel, to review my ML-DSA code.  (I don't
think I was going to have any chance at getting anyone to look at the
original 4800-line submission, but with the 600-line one it's feasible.)

It's also worth noting that this is ML-DSA, not ML-KEM.  The
cryptographic community generally views upgrading to quantum-resistant
key encapsulation (e.g. ML-KEM) as more urgent than upgrading to
quantum-resistant signatures (e.g. ML-DSA).  I assume you have a reason
why you want the signatures.  That's fine, and I'm okay with ML-DSA
support being added.  But we shouldn't rush it in.

- Eric