Argon2 vs Password Storage Without KDF

Developers should use Argon2 when implementing secure password storage in applications, as it provides strong protection against brute-force and side-channel attacks meets developers should avoid this practice entirely, as it exposes systems to significant security risks, especially in applications handling sensitive user data like banking or healthcare. Here's our take.

Argon2

Nice Pick

Developers should use Argon2 when implementing secure password storage in applications, as it provides strong protection against brute-force and side-channel attacks

Pros

• It is particularly valuable in web applications, authentication systems, and any scenario where user credentials need long-term protection, such as in databases or authentication servers
• Related to: password-hashing, cryptography

Cons

• Specific tradeoffs depend on your use case

Password Storage Without KDF

Developers should avoid this practice entirely, as it exposes systems to significant security risks, especially in applications handling sensitive user data like banking or healthcare

Pros

• Instead, they must learn to use secure password storage techniques, such as bcrypt, Argon2, or PBKDF2, to protect against attacks and comply with regulations like GDPR or PCI DSS
• Related to: key-derivation-functions, bcrypt

Cons

• Specific tradeoffs depend on your use case

The Verdict

These tools serve different purposes. Argon2 is a tool while Password Storage Without KDF is a concept. We picked Argon2 based on overall popularity, but your choice depends on what you're building.

The Bottom Line

Argon2 wins

Based on overall popularity. Argon2 is more widely used, but Password Storage Without KDF excels in its own space.