0
I would like to know in which cases I should use the various existing hash, because I know there are big differences between security and processing between them.
Is there any considered the best relative speed x safety?
2 answers
0
The most common of all is MD5, most databases already have native functions to generate this type of hash. This is also your main problem because there are already MD5 libraries on the internet, so if you want to use it add a prefix and/or a suffix something like 123456.
Whirlpool-T is recommended by the New European Schemes for Signatures, Integrity and Encryption (NESSIE), a European organisation and by ISO itself.
Personally I use MD5 after adding suffixes and prefixes and shuffling the message.
-
3
MD5 is not a safe algorithm, it is possible to break with collision algorithms, the SHA-2 or SHA-3 no longer suitable to perform a Hash. As for Salt, it is not interesting that it is a statistical and predictable value, ideally it would be to use a Guid for the service.
0
I would like to suggest a Hash algorithm, in this case BLAKE2. BLAKE was one of the finalist candidates to be the algorithm for SHA-3, but Keccak was victorious.
The second version (BLAKE2), which claims to be faster than MD5 and as strong as the current SHA-3
More about: https://leastauthority.com/blog/BLAKE2-harder-better-faster-stronger-than-MD5.html
Browser other questions tagged cryptography
You are not signed in. Login or sign up in order to post.
I think this already answers this: http://answall.com/q/2402/101
– Maniero
Just what I needed. I must remove the question @bigown?
– Giovani
I think this case would be good.
– Maniero