Talk:Post-quantum cryptography

streamlined ntru key size is incorrect

according to all sources and having calculated it myself, the public key and ciphertext sizes are in the 1k-2k range Ykulvaarlck (talk) 03:19, 13 October 2025 (UTC)

'Security Reductions' Rework

I think the 'security reductions' section should be rearranged a little, specifically broken into 'lattice-based', 'multivariate', 'code-based', 'hash-based', and 'supersingular elliptic curve isogeny' sub-sections. This lets the names be more concise/readable and only requires combining the Ring-LWE with the NTRU/BLISS subsection and the McEliece with the RLCE subsection. In the former case, I'd argue this should be done anyway as the division of the two is something of a false binary - NTRU-based schemes (including FALCON) often also rely on assuming the hardness of Ring-LWE (or its dual problem Ring-SIS). NTRU schemes utilize the same class of assumptions as Ring-LWE schemes do and just use the additional assumption that the NTRU Learning problem is hard to argue for the hardness of more standard lattice problems even over NTRU-structured lattices. In the latter case, I don't specialize in code-based cryptography, but the RLCE section itself describes these schemes as based on McEliece so combining those sections seems natural as well.

If there's no opposition to the idea, I'm happy to make the above adjustments KJack115 (talk) 23:54, 13 March 2026 (UTC)

Supersingular elliptic curve isogeny cryptography

The summary in this article makes two strong claims for its security but the linked article on the topic says that it was broken in a "devastating" demonstration in July 2022. ~2026-27082-48 (talk) 18:29, 4 May 2026 (UTC)

Edit request: chart of post-quantum key exchange support (COI disclosed)

Conflict of interest disclosure: I operate CrawlCheck (crawlcheck.io), the service whose weekly TLS probe produced the data in the chart below. I am proposing this here rather than editing the article myself, and I leave the decision to uninvolved editors.

Proposed change: add an image to the Implementation section:

[[File:Websites supporting post-quantum key exchange, November 2026.svg|thumb|Share of websites in a stratified sample of 1,295 that completed a TLS 1.3 handshake using the hybrid X25519MLKEM768 key exchange, November 2026]]

The proposed image

Why: the section describes deployment but has no measurement of how widely servers support post-quantum key exchange. The chart reports server-side support by type of site (local businesses, software companies, .gov, wider web) and by whether a CDN fronts the site. Method, sample and the full data table are on the file page; the figures are CC BY 4.0.

Limits, stated plainly: this is a self-published measurement, not a secondary source, so I am not proposing any prose or statistic for the article text, only the image with a descriptive caption. If editors prefer not to use self-published data, I understand. Vsnary (talk) 03:03, 3 November 2026 (UTC)