#PQCrypto

𝕂𝚞𝚋𝚒𝚔ℙ𝚒𝚡𝚎𝚕kubikpixel@chaos.social
2026-03-03

«Decentralized P2P Chat & File Transfer - Secure Messaging Without Central Servers:
Creating decentralized P2P technology. Aiming to provide industry-grade cryptographic capabilities encapsulated into a webapp.»

Do any of you regularly use @xoron with several people at the same time or even professionally and what is your impression about it?

🐟 positive-intentions.com

#chat #p2p #e2ee #filetransfer #security #decentralization #webtools #webapp #pqc #pqcrypto #cryptography #noserver

𝕂𝚞𝚋𝚒𝚔ℙ𝚒𝚡𝚎𝚕kubikpixel@chaos.social
2026-02-26

«Threema wird quantensicher — Partnerschaft mit IBM Research:
Der Schweizer Messenger Threema arbeitet mit IBM Research zusammen, um seine Chats quantensicher zu machen. Ziel ist Schutz vor Quantencomputern.»

Diesbezüglich ist @threemaapp nicht alleine und IBM ist so zu sagen deren Nachbar, die haben in ihrer Nähe einen PQC Standort.

heise.de/news/Threema-wird-qua

#postquantum #ibm #threema #pqc #app #pqcrypto #quantencomputer #chatapps #itsicherheit #mlkem #signal #apple #itsec #itsecurity #chat

Alexandre Dulaunoyadulau@infosec.exchange
2025-12-05

ML-KEM Mythbusting

"There have been some recent concerns about ML-KEM, NIST’s standard for encryption with Post-Quantum Cryptography, related standards of the IETF, and lots of conspiracy theories about malicious actors subverting the standardization process. "

#pqc #pqcrypto #cybersecurity #ietf

🔗 keymaterial.net/2025/11/27/ml-

2025-11-24

"Consensus means whatever the people in power want to do." -- djb

blog.cr.yp.to/20251123-dodging

#ietf #crypto #pqcrypto

CnznewsCnznews
2025-11-24

NSA and IETF, part 3

cr.yp.to: 2025.11.23: NSA and IETF, part 3 Table of contents (Access-I for index page) 2025.11.23: NSA and IETF, part 4: An example of censored dissent. 2025.11.23: NSA and IETF, part 3: Dodging the issues at hand. 2025.11.23: NSA and IETF, part 2: Corruption continues. 2025.10.05: MODPOD: The collapse of IETF's protections for…

cnznews.com/nsa-and-ietf-part-

2025-10-13

2025.10.04: NSA and IETF: Can an attacker simply purchase standardization of weakened cryptography?
blog.cr.yp.to/20251004-weakene
#PQcrypto #hybrids #NSA #IETF #antitrust

It's normal for post-quantum cryptography to be rolled out as an extra layer of security on top of traditional pre-quantum cryptography, rather than as a replacement.

For example, Google's CECPQ1 experiment was double encryption with traditional pre-quantum ECC (specifically X25519) and post-quantum NewHope1024. CECPQ2, a joint experiment between Google and Cloudflare, was ECC+NTRUHRSS701. CECPQ2b was ECC+SIKEp434. Ten SSH implementations support ECC+sntrup761. Today's usage of post- quantum cryptography by browsers is approaching half of the connections seen by Cloudfiare, where 95% of that is ECC+MLKEM768 and 5% is ECC+Kyber768

If post-quantum cryptography is designed to be super-strong, so strong that it even survives future quantum computers, then why are we keeping the ECC layer? Same reason that you wear your seatbelt: in the real world, cars sometimes crash, and seatbelts reduce the damage.
Thomas Fricke (he/his)thomasfricke@23.social
2025-10-12

Is Post Quantum Crypto dead on arrival. At least there is a strange smell!

@djb

"Can an attacker simply purchase standardization of weakened cryptography? #pqcrypto #hybrids #nsa #ietf #antitrust

It's normal for post-quantum cryptography to be rolled out as an extra layer of security on top of traditional pre-quantum cryptography, rather than as a replacement.

... looking at how easy it is for NSA to simply spend money to corrupt the standardization process."

blog.cr.yp.to/20251004-weakene

Daniel J. Bernsteindjb@cr.yp.to
2025-10-04

New blog post "NSA and IETF: Can an attacker simply purchase standardization of weakened cryptography?" blog.cr.yp.to/20251004-weakene #pqcrypto #hybrids #nsa #ietf #antitrust

𝕂𝚞𝚋𝚒𝚔ℙ𝚒𝚡𝚎𝚕kubikpixel@chaos.social
2025-08-15

»NIST standardisiert ein leichtgewichtiges Kryptografieverfahren für IoT-Geräte:
Ascon ist ein leichtgewichtiges Kryptografieverfahren, das insbesondere für IoT-Geräte wie RFID-Tags gedacht ist. NIST hat das Verfahren nun standardisiert.«

Ich habe absolut keine Ahnung von IoT aber spannend. Es sind leider sehr viele IoT-Tools, die im allgemeinen erhältlich sind, sehr unsicher im Web.

✔️ heise.de/news/NIST-standardisi

#iota #nist #pqc #pqcrypto #rfid #tools #web #internet #postquantum #kryptografie

CosicBeCosicBe
2025-07-28

🎥 Just released! Watch the COSIC Seminar "FRIttata: Distributed Proof Generation of FRI-based SNARKs" by Hua Xu (KU Leuven): youtube.com/watch?v=sMHfxYrNl5I
📄 Read the full paper on : eprint.iacr.org/2025/1285

Stéphane Bortzmeyerbortzmeyer@mastodon.gougere.fr
2025-07-24

Talk "Migrating Telecom to Quantum-Resistant Cryptography on a Global Scale" by John Preuß Mattsson

#IETF123 #PQcrypto

2025-04-09

#Qualys needs to update their TLS client test to support the new signature algorithms and named groups. There are a fair number of "unknown" entries with #OpenSSL 3.5. clienttest.ssllabs.com:8443/ss

#pqc #pqcrypto

Qualys TLS client test showing number of "unknown" signature algorithms and names groups when using OpenSSL 3.5.
Soatok Dreamseekersoatok@furry.engineer
2025-03-15

I must admit, I'm not in love with HQC but I think it's a good backup choice if ML-KEM is ever broken.

McEliece public keys would have broken my use cases.

#pqcrypto

Fiona :transbian: :autism:Fiona@blahaj.zone
2025-03-12

#NIST chose #HQC as their backup KEM and elected not to standardize #ClassicMcElice for now among other reasons pointing to the standardization with #ISO.

The argument to choose HQC over Bike is a higher confidence in IND-CCA-security of HQC. I cannot comment on whether that is a reasonable assessment, though I have no reason to doubt it, but I can say that in terms of reasons to make a choice this is of course a pretty good one.

I’m not sure how I think about the decision regarding McElice, but I can to an extend see where they are coming from.

This means there are now
9 post quantum algorithms approved, standardized or chosen for standardization by generally respected organizations:

Key Encapsulation Mechanisms (“KEMs”):

* ML-KEM (“Kyber”), based on Lattices, standardized by NIST

* HQC, based on Codes, chosen for standardization by NIST

* Classic McElice, based on codes, approved by BSI (de), ANSSI(fr), and NCSC (nl)

* Frodo, based on lattices, approved by BSI (de), ANSSI(fr), and NCSC (nl)

Signatures:

* ML-DSA (“Dilithium”), based on Lattices, standardized by NIST

* SLH-DSA (“SPHINCS+”), based on hashes, standardized by NIST

* FN-DSA (“Falcon”), based on lattices, chosen for standardization by NIST

Stateful Signatures:

* XMSS, based on hashes, standardized by IEEE

* LMS, based on hashes, standardized by IEEE

Overall, this looks like a decent portfolio. Future standardization might add schemes based on multivariate-equations and isogonies, but for now this should do and give us a basis from which we can design more efficient schemes without being to concerned about the entire ground suddenly giving in because one random guy/gal finds a new attack-vector.

#postquantumcryptography #PQC #PQCrypto

Fiona :transbian: :autism:Fiona@blahaj.zone
2025-02-24

So looking through some old projects I’ve had lying around, I ran into something I started (and never even really wrote anything) about steganography. This led me down a bit of rabbit-hole and I now have a slightly better understanding of some components of ML-KEM (aka. #Kyber).

Both the public key and the ciphertext are for the most part long sequences of integers modulo 3329 that are effectively indistinguishable from random integers out of that range.

Of course they are obvious to distinguish from random bitstrings, but the easiest way to fix that would be to just view them as numbers in base 3329, re-encode them to base 2 and work from there… So that might be one thing I could look into now.

The alternative is to see whether there is a sufficiently hard to detect way to change some of the representatives of the field-elements… It might be easier to implement if, if not easier from a mathematical perspective, but would also let the possibility of slightly compressing the public-key and ciphertext by about 2.5% in length lie on the table.

In any case, this is something that might be worthwhile for practical use-cases…
🤔

#cryptography #pqc #pqcrypto #steganography #crypto #MLKEM

2024-11-04
[RSS] TLS 1.3 Hybrid Key Exchange using X25519Kyber768 / ML-KEM

https://www.netmeister.org/blog/tls-hybrid-kex.html

#cryptoraphy #tls #pqcrypto
2024-09-20

#OpenSSH 9.9 has been released: openssh.com/txt/release-9.9

The significant new feature is support for post-quantum mlkem768x25519-sha256 KEX as specified in datatracker.ietf.org/doc/html/

#pqcrypto #postquantumcryptography

:awesome:🐦‍🔥nemo™🐦‍⬛ 🇺🇦🍉nemo@mas.to
2024-06-10

Gear up for the quantum era! 🔐⚛️ Check out Kicksecure's guide on Post-Quantum Cryptography (PQCrypto) with info on quantum-resistant tools like Codecrypt, Cyph, and more. 💻🔑 #PQCrypto

kicksecure.com/wiki/PQCrypto

#privacy #security

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst