[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1551502.1769005280@warthog.procyon.org.uk>
Date: Wed, 21 Jan 2026 14:21:20 +0000
From: David Howells <dhowells@...hat.com>
To: Eric Biggers <ebiggers@...nel.org>
Cc: dhowells@...hat.com, Lukas Wunner <lukas@...ner.de>,
Ignat Korchagin <ignat@...udflare.com>,
Jarkko Sakkinen <jarkko@...nel.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
Luis Chamberlain <mcgrof@...nel.org>,
Petr Pavlu <petr.pavlu@...e.com>, Daniel Gomez <da.gomez@...nel.org>,
Sami Tolvanen <samitolvanen@...gle.com>,
"Jason A . Donenfeld" <Jason@...c4.com>,
Ard Biesheuvel <ardb@...nel.org>,
Stephan Mueller <smueller@...onox.de>, linux-crypto@...r.kernel.org,
keyrings@...r.kernel.org, linux-modules@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v13 05/12] modsign: Enable ML-DSA module signing
Eric Biggers <ebiggers@...nel.org> wrote:
> If OpenSSL 3.5 is the last version that doesn't support the noattr case,
> that would mean that OpenSSL 3.6 does support it, right? OpenSSL 3.6
> was released several months ago. Yet the above code requires version 4.
3.5 and 3.6 support ML-DSA, but not with CMS_NOATTR, so I need to update this.
Version 4 will support ML-DSA with CMS_NOATTR, but that's not yet tagged.
> How about we just support the new way only? That would be simpler, and
> it sounds like it's already supported by the latest OpenSSL.
Depends what you mean by "latest OpenSSL". Latest in git, yes; latest in
distributions that people can simply install as an rpm/deb/etc., no.
Now, assuming OpenSSL releases v4 sometime in the spring, I would probably be
fine with saying you have to have OpenSSL v4 if you want ML-DSA; but others
might have a different opinion.
David
Powered by blists - more mailing lists