best-practice development reading-list

As everyone knows, "temporary fixes" are nothing but temporary.

Unfortunately, the same is true for cryptography: unless security is your core value-proposition, crypto algorithms are almost never updated, and that's how we end up with SHA1-hashed password in 2024 🤦‍♂️

You can be sure that most projects you started in this decade will still use the same cryptographic algorithms in 2035. Therefore, it may be a good use of our precious time to study which hash functions will still be considered relevant and secure in 2030 and beyond.

We will compare the 3 most used and deployed hash functions in the wild: SHA2 (SHA-256 & SHA-512), SHA3 (SHA3-256 & SHA3-512) and BLAKE3.

We will evaluate these functions on 3 points:

  • Speed, because nobody like to wait for slow computers to crunch numbers.
  • Security, because cryptography is about providing security, after all.
  • Availability, because you should never implement crypto primitives by yourself.

But first, a short reminder of what are hash functions, how they are used, and when they should not be used.

continue reading on kerkour.com

⚠️ This post links to an external website. ⚠️

You might also like:

If this post was enjoyable or useful for you, please share it! If you have comments, questions, or feedback, you can email my personal email. To get new posts, subscribe use the RSS feed.