And co-authored the "another look" papers at https://anotherlook.ca/

If your needs are this simple, you may be better served by an opinionated crypto library like Monocypher [0] or libsodium [1]. Just look at the latter's FAQ page and you'll see they're taking your approach targeting developers, not cryptographers.

They'll provide you one blessed algorithm for every primitive with secure alternatives if your use-case demands them. XChaCha20-Poly1305 for encryption, EdDSA for signatures, X25519 for key exchange, BLAKE2b for a hash, Argon2i for a KDF.

[0] https://monocypher.org/

[1] https://doc.libsodium.org/doc/quickstart

Google’s Tink crypto library had a slightly technical page to help with that: https://developers.google.com/tink/choose-primitive

It's not new, and some people would disagree on some minor elements -- but a good place to start was regularly this blog from approximately Matasano/NCC Group members, called Cryptographic Right Answers [1]. It's very clear, gives straight forward answers in clear fashion -- and with multiple opinions often aligning.

It was updated a few times, I wonder if the equivalent exists for PQ?

Edit/Update: Found the PQ one @ [2], definitely check it out!

Maybe I'm mis-remembering, but perhaps the most controversial element was the regular recommendation of AES-GCM. It certainly has excellent security properties, but also a certain brittleness re: nonces.

[1] https://www.latacora.com/blog/2018/04/03/cryptographic-right... [2] https://www.latacora.com/blog/2024/07/29/crypto-right-answer...

> Like, I need to authenticate that a client is a known identity. What algo?

In this case, you're asking the wrong question.

When people say "what algo?" in such a context, the answers will be flavored as "Ed25519 vs secp256k1 vs RSA-PKCS1v1.5" when you should first be asking "what level of abstraction am I dealing with?" and "what are the constraints?"

Like, maybe "algo" isn't even a relevant concern.

If I were designing a simple token-based auth scheme today, I'd reach for PASETO. Unless I need interop with a third-party provider, who almost universally use JWTs and prevent me from having any say or choice in the matter.

With PASETO, you don't need to know, or even care, about "what algo?" You only need to consider mode, which is more of a use-case question.

But with JWTs, you not only have to care about "what algo?" your system needs to be very delicate in how it processes them. https://www.howmanydayssinceajwtalgnonevuln.com

I cannot imagine proactively writing a cheat sheet for every possible use case. You might be tempted to use AI to solve this problem on demand, but the cost of a hallucination here is pretty high.

If you find yourself regularly asking this question, I'd recommend just hiring a cryptography consultant.

Update: I have found https://cryptobook.nakov.com/

I think it‘s pretty good.

I wrote a deep dive into this in 2020, but not much has changed since then.

https://soatok.blog/2020/07/12/comparison-of-symmetric-encry...

EDIT: Actually, the parts about OPAQUE are no longer relevant because they changed the protocol before the RFC was final to not need encryption, but that was just an example of where you'd make this sort of trade-off decision, so the rest of the article is still relevant.