linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephan Mueller <smueller@chronox.de>
To: Simo Sorce <simo@redhat.com>,
	Ignat Korchagin <ignat@cloudflare.com>,
	David Howells <dhowells@redhat.com>,
	James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	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, linux-crypto@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Module signing and post-quantum crypto public key algorithms
Date: Fri, 13 Jun 2025 19:55:12 +0200	[thread overview]
Message-ID: <13066544.VsHLxoZxqI@tauon> (raw)
In-Reply-To: <3081793dc1d846dccef07984520fc544f709ca84.camel@HansenPartnership.com>

Am Freitag, 13. Juni 2025, 19:50:22 Mitteleuropäische Sommerzeit schrieb James 
Bottomley:

Hi James,

> On Fri, 2025-06-13 at 13:33 -0400, Simo Sorce wrote:
> > Premise: this problem can't be ignored, even if you think Quantum
> > Computers are BS, various government regulations are pushing all
> > commercial entities to require PQ signatures, so we have to deal with
> > this problem.
> 
> I agree it's coming, but there's currently no date for post quantum
> requirement in FIPS, which is the main driver for this.

Perhaps [1] should be considered if you refer to FIPS?

Further, [2] also gives a timeline.

[1] https://csrc.nist.gov/pubs/ir/8547/ipd

[2] https://www.nsa.gov/Press-Room/News-Highlights/Article/Article/3148990/
nsa-releases-future-quantum-resistant-qr-algorithm-requirements-for-national-
se/

Ciao
Stephan



  reply	other threads:[~2025-06-13 17:55 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 17:33   ` Simo Sorce
2025-06-13 17:50     ` James Bottomley
2025-06-13 17:55       ` Stephan Mueller [this message]
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
2025-11-11 18:38                 ` David Howells
2025-06-13 15:42 ` 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=13066544.VsHLxoZxqI@tauon \
    --to=smueller@chronox.de \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=cllang@redhat.com \
    --cc=dbohanno@redhat.com \
    --cc=dhowells@redhat.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=simo@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).