and here is a challenge:
this is the sha1 hash of my bitcointalk password, have fun hacking my Hero Member account:
*snip*
Not quoting, coz if this checksum is not salted it might have been a very bad idea to post it.
first of all its just an account
secondly the point is you can NOT reverse it to find my real password which is long and hard AF!
this is the crappy old SHA1 we are talking about.
a password hash is not as easily broken as you may think. it is called an irreversible hash function for a reason!
this means if btc-e used a proper way to save the password and hashed them properly using salt,... then it is impossible to crack them.
In reality decrypting a large SHA-1 hash is nearly impossible. But since SHA-1 maps several byte sequences to one, you can't "decrypt" a hash, but in theory you can find collisions: strings that have the same hash. IMHO.
collision is no longer "in theory" google already successfully produces a collision with SHA1 and it took them about 2^63.1 SHA1 evaluations and it is about 110 years of single GPU calculation.
but it has nothing to do with "reversing and finding the password" someone with that much computation power can only reproduce the same hash as my original password have fun holding the same hash for another string for no reason
