Same hash for integer

[pvorb]

Same hash for integer

[tobscher]

It looks like in its current state md5(12345) and md5('12345') will still return different results. I am wondering if this is due to the fact that Strings get converted into byte arrays and integers are not. What is the expected outcome?

[pvorb]

In its current state the algorithm expects strings or byte arrays as messages (see line 11). I should have noted that in the Readme.

Nevertheless, I should simply fix that behavior by adding a toString() for other values than string and byte array.

[pvorb]

Calling md5 with something different than strings or buffers is undefined behaviour.

Tobias Haar [email protected] schrieb:

It looks like in it's current state md5(12345) and md5('12345') will still return different results. I am wondering if this is due to the fact that Strings get converted into byte arrays and integers are not. What is the expected outcome?

---

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#3 (comment)

[zneuron]

the result of md5(12345) and md5('12345') should be same, i don't understand why not now; if the message is not strings or buffers, it should be converted to string at first, and then return the md5 value