#quantique #cryptographie #PQC
J'apprends le terme de Q-day, qui désigne le jour où un CRQC (Cryptographically Relevant Quantum Computer, prononcer "cric") cassera tout. Le Q-day, selon les meilleurs experts, est entre deux et cent ans dans le futur.
C'est même déjà dans Wikipédia anglophone https://en.wikipedia.org/wiki/Q-Day
OpenSSH 10.0 just landed, now completely removing DSA signature support (you've been warned, repeatedly :-) and finite-field diffie-hellman key exchange. It also enables mlkem768x25519-sha256 as the default kex! (#pqc)
The new version string ("OpenSSH_10.0") is also likely to confuse a bunch of stupid scanners that assume anything starting with "OpenSSH_1" is a 1.x version.
This is undoubtedly the most promising Post-Quantum TLS deployment situation I have seen for #Tor since we started discussing it more actively in the team. Very exciting!
I hope that OpenSSL 3.5, when released, will make it into #Debian Trixie. That would make deployment of this so much more snappy and easy for the Tor network to upgrade, but that may be dreaming. The timelines here look quite difficult for that to happen, but let's hope.
This Venn diagram showing which PQ algorithms are permitted by which government regulatory body from Mike Ounsworth's presentation at the Real World Post-Quantum Cryptography Workshop last week.
(Mike gave a version of that talk earlier this year at the PKIC conf: https://pkic.org/events/2025/pqc-conference-austin-us/WED_BREAKOUT_1200_Mike-Ounsworth_Architecting-PKI-Hierarchies-for-Graceful-PQ-Migration.pdf)
Sicherheits-Architekt. Wenn du vormittags elliptische Kurven für die Post-Quanten-Kryptographie evaluieren darfst und nachmittags einem Projektmanager erklären musst, dass das Telefon kein sicherer Kanal ist.
Post-Quantum #DNSSEC Testbed with BIND and PowerDNS
…ja und nein und vor allem ist es Marketing durch Angstmacherei. Quantenkomputer sind noch nicht wirklich einsetzbar obwohl es viele als solches gerne vermarkten.
»Quantenschlüssel aus der Sicht des CISO:
Quantentechnologien – ein Sicherheitsrisiko oder das Mittel der Wahl gegen Cyberangriffe? Warum, für wen und wo es wichtig ist, die Integration von Quantentechnologien zu starten.«
https://www.csoonline.com/article/3846875/quantenschlussel-aus-der-sicht-des-ciso.html
»The Quantum Apocalypse Is Coming. Be Very Afraid:
What happens when quantum computers can finally crack encryption and break into the world’s best-kept secrets? It’s called Q-Day—the worst holiday maybe ever.«
Since this is very much for us, I cannot deny it, but I see it as a marketing propaganda. To scare is also a marketing strategy.
https://www.wired.com/story/q-day-apocalypse-quantum-computers-encryption/
Out of the top 100K domains, roughly 28K negotiate a quantum safe key exchange.
Almost all of those support both x25519_kyber768 and X25519MLKEM758; only 129 sites support SecP256r1MLKEM768. There are _no_ sites that support pure #PQC via e.g., mlkem768.
The overwhelming majority of sites that support PQC do so by way of Cloudflare. That percentage matches Cloudflare's overall coverage of the top 1M domains.
Just in time for Real World PQC Workshop:
I took at a look at who currently supports #PQC. The answer will not surprise you at all.
…neben dem vorhin erwähnten Marketing bezüglich des Post-Quantom Kryptografie ist darauf hin auch wieder die Angsmacherei davon. Das die mal angewendet wird ist klar aber wie ist die Frage.
»Ihre Passwörter sind bald wertlos: Quantencomputer knacken alles!
Quantencomputer revolutionieren die Rechenleistung. Sie lösen hochkomplexe Aufgaben in Sekundenschnelle. Doch die Technologie birgt auch Gefahren.«
07.03.2025: GnuPG announces release of 2.5.5 for public testing, finalized PQC algorithms are supported.
Source: https://lists.gnupg.org/pipermail/gnupg-announce/2025q1/000491.html
11.03.2025: NIST selects HQC as fifth algorithm for post-quantum encryption.
Source: https://www.nist.gov/news-events/news/2025/03/nist-selects-hqc-fifth-algorithm-post-quantum-encryption
PQC: https://wikipedia.org/wiki/Post-quantum_cryptography
GnuPG: https://mastodon.online/@blueghost/111974048270035570
Harvest now, decrypt later: https://mastodon.online/@blueghost/111357939714657018
#JDK24 was released yesterday! This is a significant release for Java Security, as it contains two new core Quantum-Resistant cryptographic algorithms, ML-KEM for Key Encapsulation, and ML-DSA for Digital Signatures.
"Time to be crypto* agile, not fragile." - good criticism of the IETF's slow move on post-quantum cryptography adoption. "Stop getting in the way of consensus."
https://datatracker.ietf.org/meeting/122/materials/slides-122-pquip-ietf-is-quantum-fragile-01.pdf
* "crypto" means cryptography; always has, always will
Post Quantum Migration of Tor. It will be interesting to see when the Tor Project starts implementing #PQC in arti and tor:
https://eprint.iacr.org/2025/479.pdf #cryptography #tor #privacy
NIST selects HQC (Hamming Quasi-Cyclic -- https://pqc-hqc.org/) for standardization as the second #PQC key-encapsulation mechanism after ML-KEM.
But no rush, "the final version will be published in approximately two years".
https://groups.google.com/a/list.nist.gov/g/pqc-forum/c/w-6RREtb7-c/m/vRjBJE3dAAAJ
#OpenSSL will get the now standardized post-quantum cryptography algorithms (ML-KEM, ML-DSA, SLH-DSA) in 3.5 (planned release date is 2025-04-08):
https://openssl-library.org/post/2025-02-04-release-announcement-3.5/
This will include X25519MLKEM768, and will be enabled and preferred by default:
https://mailarchive.ietf.org/arch/msg/tls/g9sagkuAu8KlWpmJ30YdXbga5Xg/
Scientists create world's 1st chip that can protect data in the age of #QuantumComputing attacks
Anoxinon e.V. 
