So long as the hash wasn't generated using a salt there is a decent chance that you can generate a collision in a reasonable amount of time. My concern is, why do you need to decrypt a password in your own database. Couldn't you just change the hash to that of a password you already know?
So long as the hash wasn't generated using a salt there is a decent chance that you can generate a collision in a reasonable amount of time. My concern is, why do you need to decrypt a password in your own database. Couldn't you just change the hash to that of a password you already know?
And if you need one to plug in there one of us can help you out with a generic one. Then once you login you just change it again.
MD5 is a one-way encryption, meaning the only way to find out what something (for example a password in a database) is to go through every combination.
Some websites have done this (Look for md5 rainbow tables), though this is limited to basic words/phrases.
__________________
My Blog/Site: Please login or register to view this content. Registration is FREE
That site is the reason why passwords should be encrypted with a salt. vBulletin does it and so should you
Better yet, don't use md5 at all. Use sha1 and a salt and the chances of your passwords being decrypted are virtually zero. The added entropy also prevents collisions
Wtf. If your password is not qwerty or 123 or any dictionary word there is no difference between sha1 and md5 because both will take infinity to decrypt if the only way to check the password is applying it to login form. And considering that to decrypt the password you should first obtain its hash in some way the task becomes completely impossible.
Wtf. If your password is not qwerty or 123 or any dictionary word there is no difference between sha1 and md5 because both will take infinity to decrypt if the only way to check the password is applying it to login form. And considering that to decrypt the password you should first obtain its hash in some way the task becomes completely impossible.
Are you saying you should assume that the users of the application you code will know better than to use dictionary words as passwords? Besides, I am not suggesting that a brute force attack be used to decrypt either, there are better ways.
I guess that if your data is so valueable that the password decryption can be used there are better ways to steal that data, e.g. using system security holes, not the script ones.