August 15th, 2024

Cryptographic Right Answers: Post Quantum Edition

Post-quantum cryptography is essential as quantum computers threaten classical systems. NIST is standardizing algorithms, but challenges include differing properties, larger key sizes, and the need for a hybrid security approach.

Read original articleLink Icon
ConcernAppreciationCuriosity
Cryptographic Right Answers: Post Quantum Edition

Post-quantum cryptography (PQC) is becoming increasingly important as quantum computers pose a potential threat to classical cryptographic systems. The urgency for migration to PQC arises from the possibility that quantum computers capable of breaking current algorithms could emerge within the next two decades. Governments, including the U.S., are taking steps to prepare for this transition, with NIST leading efforts to standardize PQC algorithms. The NIST contest has already identified several promising algorithms, including Dilithium, Falcon, SPHINCS+, and Kyber, which are designed to withstand both classical and quantum attacks. However, the transition to PQC is complicated by the fact that these new algorithms often have different properties and trade-offs compared to classical systems, making it challenging to provide straightforward recommendations. Additionally, the larger key sizes and artifacts associated with PQC can create compatibility issues with existing systems. The article emphasizes the need for a hybrid approach that combines classical and post-quantum algorithms to leverage the strengths of both while ensuring security against future threats. As the landscape of cryptography evolves, ongoing research and development will be crucial to address the challenges posed by quantum computing.

- Quantum computers could threaten current cryptographic systems within 20 years.

- NIST is standardizing post-quantum cryptography algorithms to prepare for this transition.

- New PQC algorithms have different properties and trade-offs compared to classical systems.

- Larger key sizes in PQC may lead to compatibility issues with existing technologies.

- A hybrid approach combining classical and PQC algorithms is recommended for enhanced security.

AI: What people are saying
The comments reflect a range of concerns and insights regarding post-quantum cryptography (PQC) and its implications.
  • Discussion on the larger key sizes of PQC algorithms and their impact on resource-constrained devices like mobile and IoT.
  • Concerns about the practical readiness of PQC solutions and the risks associated with implementing them in production environments.
  • Questions about the effectiveness of classical defenses against potential quantum attacks, particularly the "store now, decrypt later" threat.
  • Calls for regular updates on cryptographic standards to ensure ongoing relevance and security in a rapidly evolving field.
  • Criticism of reliance on NIST and FIPS regulations, suggesting that they may contribute to vulnerabilities in cryptographic implementations.
Link Icon 12 comments
By @Rhapso - 6 months
There are tables at the end describing the algorithms key sizes. be mindful of "(Size in bytes)" not bits. They cover that these algorithms use bigger keys, but it is 4 kilobytes.
By @kaliszad - 6 months
Thank you for the update. This is really useful. It would be really great, if you could commit to an update a few years down the road at the latest. E.g. "I will release an update no later than August 15th 2027". 3 years in the fast-changing world shouldn't be such a burden and it would help to settle many discussions somewhat reasonably with appeal to authority :-D No seriously, having something that can be considered current advice would be great.
By @librasteve - 6 months
Good list of early supporters near the bottom of the post text - Chrome, OpenSSH and iMessage are relevant for me.
By @ccppurcell - 6 months
As I understand it, the only reason pqc is of "practical" concern is the issue of "store now, decrypt later".

Is it possible to defend against this attack in a classical way? Some sort of time limit on decryption? Or an argument that it's impossible?

By @BoppreH - 6 months
Excellent post, I've always recommended people to this series.

I'm curious what's the general opinion on the production-readiness of these solutions. Open Quantum Safe, for example, discourages it's use in production, and recompiling nginx to use PQC-BoringSSL feels risky since I'm not intimately familiar with both projects ("did I miss a --enable-security flag?").

> the PQ keys are 4 orders of magnitude larger

For McEliece, perhaps, but the algorithms in the tables are "only" 2 orders of magnitude larger.

By @rgovostes - 6 months
“Classical cryptography” used to refer to historical ciphers, Vigenère and the like, tapering off after the World War 2-era cipher machines and definitely not used to describe asymmetric algorithms. There should be a different term for pre- (non-?) quantum cryptography from the modern era. We already suffered the redefinition of “crypto”.
By @throw0101d - 6 months
NIST announcement:

* https://www.nist.gov/news-events/news/2024/08/nist-releases-...

See

* FIPS 203, Module-Lattice-Based Key-Encapsulation Mechanism Standard (ML-KEM / CRYSTALS-KYBER)

* FIPS 204, Module-Lattice-Based Digital Signature Standard (ML-DSA / CRYSTALS-Dilithium)

* FIPS 205, Stateless Hash-Based Digital Signature Standard (SLH-DSA / SPHINCS+)

From:

* https://csrc.nist.gov/News/2024/postquantum-cryptography-fip...

* https://www.federalregister.gov/documents/2024/08/14/2024-17...

By @1oooqooq - 6 months
Hostly, most cryptographic vulnerability today are because things are stuck in the NIST and FIPS regulation. Most vulnerable building blocks are still shipped to have their certification to begin with. Why there's still excitement to their work?
By @michaelt - 6 months
I've always found it a bit disquieting how many times people feel the need to update these "cryptographic right answers" blog posts.

This is what, a fourth or fifth version since 2009?

Meanwhile everything from ubuntu's apt-get to my connection to HN is secured with 2048-bit RSA - an algorithm invented in 1977 and in widespread use since at least 1995.

Am I getting crypto advice that will keep my data safe for 30+ years, if the advice changes every 3 years?

By @upofadown - 6 months
>Avoid: HMAC-MD5, HMAC-SHA1 and such. The underlying hash function has to be safe.

Interestingly enough, there is a proof out there that more or less states the opposite for HMAC-MD5 and HMAC-SHA1:

* https://eprint.iacr.org/2006/043.pdf

The issue here is that MD5 and SHA1 are broken for collisions. But no one could figure out an actual attack for HMACs based on them. The linked paper is an attempt to explain that.

By @Ahmed_rza - 6 months
Great post! I was worried for a long time about this thing as I'm also working in DeFi field. It's great that governments are taking the quantum computer threat seriously