# Cryptographic Right Answers: Post Quantum Edition

DevFeed: [Cryptographic Right Answers: Post Quantum Edition](<https://devfeed.tech/articles/cryptographic-right-answers-post-quantum-edition-29194.md>)

Original publisher: [Read original article](<https://www.latacora.com/blog/post-quantum-cryptographic-right-answers/>)

Published: 2024-07-29T17:25:48Z

Content type: article

Language: en

Sources: [Latacora](<https://devfeed.tech/sources/latacora.md>)

Topics: [Post-quantum cryptography](<https://devfeed.tech/topics/post-quantum-cryptography.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [recommendations](<https://devfeed.tech/topics/recommendations.md>)

Tags: [academic-research](<https://devfeed.tech/tags/academic-research.md>), [cryptography](<https://devfeed.tech/tags/cryptography.md>), [guide](<https://devfeed.tech/tags/guide.md>), [post-quantum-cryptography](<https://devfeed.tech/tags/post-quantum-cryptography.md>)

## AI overview

This article updates cryptography recommendations for the transition to post-quantum cryptography. It explains that PQC involves more varied tradeoffs than classical cryptography and that some promising systems have failed, making recommendations harder to assess confidently.

## Source excerpt

One of our favorite blog posts is our "crypto right answers" post. It's intended to be an easy-to-use guide to help engineers pick the best cryptography choices without needing to go too far down a rabbit hole. With post-quantum cryptography (PQC) recently transitioning from an academic research topic to a more practical cryptography concern we figured it's time for an update of our cryptography recommendations. One thing that makes recommending PQC challenging is that historically, we've been able to provide "better" answers for classical cryptography. Faster and bigger hashes, stronger password KDFs, easier-to-use primitives... These things all have the same fundamental "shape": you can take an existing design and drop in something else to make it better. MD5 and BLAKE3 are not comparable in strength, but you can just use BLAKE3 in place of MD5 and get something that's just far better with minimal API changes.