Generalized Secure Hash Algorithm
tedunangst.com
tedunangst.com
One of the primary concerns for PHC was making an algorithm which is hard to speed up on custom hardware. Bill Cox, Solar Designer, et al. went at this very hard, and I think their approach will turn out to be favored.
I'm a little bit concerned that if the algorithm is now flexible enough, to not be implemented efficiently in a more generalized circuit, then is it flexible enough to behave possibly erratically?
But I'm not even sure if this GSHA type algorithm really would be all that difficult to implement in an ASIC.
Of course, the great thing is that an algorithm promising such benefits is in high demand, Proof-of-Work algorithms, and so anything which shows merit will probably be explored and tested.
It's also assuming that the constants don't matter for the security of the hash function. They do.
Isn't the cost of an ASIC containing an MD5+SHA1 algorithm about the same as the cost of an ASIC containing only one of them?
from crypto to bcrypt to scrypt
Hang on. I thought the consensus was to use bcrypt. Is scrypt better now?Pretty sure collisions are a practical concern for password hashing... More collisions = more "valid" passwords for a given account.
* It's not the case of security through obscurity, as there is no secrecy of the algorithm design.
(As a side note, I don't see how this algorithm prevents cheap hardware implementations of it.)