0

I may be wrong here, but from what I understand, no 2 hashes are ever the same. Certainly, when I md5 the word "password" twice, I get two different hashes.

If the user's password is "password123", then the hash will be something like "482c811da5d5b4bc6d497ffa98491e38"

If the user enters their password when logging in at a later date, the hash of password123 is: "286755fad04869ca523320acce0dc6a4"

How can I compare the 2 hashes if they're different for the exact same word?

kttr
  • 414
  • 1
  • 3
  • 11

2 Answers2

2

Hash of same value with the same algorithm is always the same - this is why it is ok to compare just hashes to verify if values are definitely different (if hashes are the same it may still mean values are different, but using sufficiently long hash like SHA256 it may be safe enough to assume that values are the same for password verification).

Most likely you have bug in getting original values to be represented the same way (i.e. non-trimmed spaces, different encoding,...) and that causes hashes to be different.

Note MD5 is generally not acceptable for hashing passwords due to known weakness.

Alexei Levenkov
  • 98,904
  • 14
  • 127
  • 179
  • I mixed up the hashes for "password" and "password123" by accident! What's the safest way to store passwords if not md5? Is a salt+sha256 good enough? – kttr Apr 07 '14 at 05:09
  • @Ajax - I'm not an expert on the topic - and you need to make call on your security decisions. Clearly not MD5. You can search similar questions (some are shown as "related" to your question)... I.e. http://stackoverflow.com/questions/401656/secure-hash-and-salt-for-php-passwords?rq=1 – Alexei Levenkov Apr 07 '14 at 05:15
1

Please start by reading How to securely hash passwords?.

I'll leave most of the detail in my answer to Password Verification - How to securely check if entered password is correct, but the high points are:

  • Hashes are deterministic; however, for password hashes, a per-user random salt of 8-16 bytes is generated when users select passwords
    • and the salt is saved in the clear with the user's password hash, iteration/work factor (see below), and the version of password hashing you're using (so you can change it easily)
    • thus during verification, you use the same salt you did before
  • Passwords should not be hashed using a single pass of any hash function.
  • Passwords should be hashed using PBKDF2, BCrypt, or SCrypt.
    • For PBKDF2 in particular, do not select an output size larger than the native hash size.
    • In all cases, select as high an iteration count as you can afford during expected peak times.
Community
  • 1
  • 1
Anti-weakpasswords
  • 2,604
  • 20
  • 25