<snip> Firstly, I need to find out which hash is used by rom itself for encryption. If it's system crypt() (highly doubtful, but maybe), then I'll go about my merry way and try to figure out what I'm doing wrong elsewhere. </snip>
It IS system crypt(). So rest assured there. ANY insignificant thing might cause this to hash up... I haven't used *SQL databases yet so I can not say for sure, but are there any special symbols or such that the string datatype uses as an escape character in some form? Or possibly the reading/writing from/to the database is sneaking in a space or dropping non-printable characters, since crypt can return string with any number from 0-255 (the standard ASCII range, or char size, depending on how you want to look at it...) <snip> IF it's not that (or otherwise php compatible) then I need to find out how to decrypt the password, without changing everything to clear passwords. Is it THAT hard of a question to ask which hash is used? </snip> Btw, crypt does some pretty funky stuff in its process that makes it so the password can NOT be decrypted. Any password encryption routine that is worth a grain of salt (no pun intended...well maybe...) is unable to be decrypted. That is why you can not use a linux admin tool to view passwords of users on your system, or even in windows, you are unable to view user's passwords. This is why dictionary attacks and brute forcing came about...since that was the only way to 'guess' a password: encrypting a string in the same method as what you are trying to 'guess' and comparing the two. Ammaross Danan
