From: Simo Sorce <simo@redhat.com>
To: "Elliott, Robert (Servers)" <elliott@hpe.com>,
David Howells <dhowells@redhat.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Ignat Korchagin <ignat@cloudflare.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Stephan Mueller <smueller@chronox.de>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
Paul Moore <paul@paul-moore.com>, Lukas Wunner <lukas@wunner.de>,
Clemens Lang <cllang@redhat.com>,
David Bohannon <dbohanno@redhat.com>,
Roberto Sassu <roberto.sassu@huawei.com>,
"keyrings@vger.kernel.org" <keyrings@vger.kernel.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Module signing and post-quantum crypto public key algorithms
Date: Tue, 11 Nov 2025 11:14:59 -0500 [thread overview]
Message-ID: <1ce413b202ca7c008e077a6f1cfa88f94a3a7cbd.camel@redhat.com> (raw)
In-Reply-To: <IA4PR84MB4011485C0EFFFF9F2820A1BFABC1A@IA4PR84MB4011.NAMPRD84.PROD.OUTLOOK.COM>
On Sun, 2025-11-09 at 19:30 +0000, Elliott, Robert (Servers) wrote:
> The composite motivation is to provide some protection if someone
> discovers a basic flaw in the PQC algorithm. If quantum computers
> haven't arrived yet to break the traditional algorithm, the
> composite still proves validity.
Given you quoted me wrt composite signatures, I'd like to make clear I
do *not* necessarily favor it.
Unlike regular software or firmware, kernel modules are generally tied
to a specific version of the kernel, therefore there is no real need
for long term resistance (unless you plan to never upgrade a kernel).
If a defect in a signing algorithm is found you can simply distribute a
new kernel with modules resigned with a different algorithm.
The problem of using composite algorithms are many:
- You need composite keys (or at least two keys, depending on the
implementation).
- You will pay a higher price in terms of CPU/time for verification for
each signature.
- You will pay a higher price in terms of disk/ram space to store
multiple signatures.
It is generally not worth paying this price when the remediation is
easy.
--
Simo Sorce
Distinguished Engineer
RHEL Crypto Team
Red Hat, Inc
next prev parent reply other threads:[~2025-11-11 16:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 14:54 Module signing and post-quantum crypto public key algorithms David Howells
2025-06-13 15:21 ` Ignat Korchagin
2025-06-13 15:42 ` David Howells
2025-06-13 17:33 ` Simo Sorce
2025-06-13 17:50 ` James Bottomley
2025-06-13 17:55 ` Stephan Mueller
2025-06-16 14:02 ` Simo Sorce
2025-06-16 15:14 ` James Bottomley
2025-06-16 17:27 ` Simo Sorce
2025-06-19 18:49 ` Stefan Berger
2025-11-07 10:03 ` David Howells
2025-11-07 10:23 ` Stephan Mueller
2025-11-07 19:19 ` Stefan Berger
2025-11-07 23:10 ` Elliott, Robert (Servers)
2025-11-08 7:46 ` David Howells
2025-11-09 19:30 ` Elliott, Robert (Servers)
2025-11-11 16:14 ` Simo Sorce [this message]
2025-11-11 18:38 ` David Howells
2025-06-13 15:43 ` Linus Torvalds
2025-06-13 16:13 ` James Bottomley
2025-06-13 16:32 ` Roberto Sassu
2025-06-13 16:34 ` Stephan Mueller
2025-06-13 17:04 ` Eric Biggers
2025-06-19 12:31 ` Lukas Wunner
2025-06-19 23:22 ` Herbert Xu
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=1ce413b202ca7c008e077a6f1cfa88f94a3a7cbd.camel@redhat.com \
--to=simo@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=cllang@redhat.com \
--cc=dbohanno@redhat.com \
--cc=dhowells@redhat.com \
--cc=elliott@hpe.com \
--cc=herbert@gondor.apana.org.au \
--cc=ignat@cloudflare.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=smueller@chronox.de \
--cc=torvalds@linux-foundation.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