-
-
CommentAuthorJJenZz
- CommentTimeDec 5th 2007 edited by JJenZz on the 05th December 2007 at 10:20:48 EST
I posted the following in another topic, but wanted to create a new one because I thought it mightn't get read where it is and I am quite concerned...Posted By: ChristopherOh and how silly can you be? You used the same (extremely simple and unsecure) password - 7 letters, all lowercase, yes I know what it was - for both accounts... you may want to change that now eh?
I dunno about anyone else, but personally i'm wondering how you know his password? Surely all passwords are securely encrypted apon registering? I am a little shocked to say the least
-
-
- CommentAuthorpapab30
- CommentTimeDec 5th 2007
If it's an MD5 hash, then the encryption is one way. There is no way to read that password, but you can compare it against other encrypted strings to see if the lengths are the same. But as in knowing what the data itself is........very difficult. -
-
CommentAuthorChristopher
- CommentTimeDec 5th 2007
Sorry I haven't read any other threads since yesterday but thought I should reply to this ASAP.
Yes it is an MD5 hash, which you are right in saying is one way, but there are many tables of MD5 sums available for searching, and unfortunately it was neccessary to decode the password to try and narrow out the possibility of coincedence before accusing someone of duplicate accounts used for abuse.
Upon noticing the abusing user account, first thoughts were to check IPs, both were the same (static) IP address, that was strike one, strike two came when comparing the MD5 hashes of both user accounts as they were the same (the only 2 accounts with this hash as well), but of cause 2 people may have the same password, so this could have been a coincedence, which is why I used a brute force method on it to check it wasn't purely password or the like, as the password wasn't something "disposable" it was too much of a coincedence.
But in short, the database is securely protected on the server, access is not only restricted, but the MySQL user password in use is ridiculously long and contains a huge range of special characters, without this database access I wouldn't have been able to touch the MD5 hash even, but once people have access to hashed passwords, you should know that all basic passwords (1 - 7 characters (not mixed cased or alphanumeric)) are easy to decode within an hour at most using a brute force method.
Just making it 8 characters long and including a single number or special character would have made it near impossible to decode, so I think the real thing people should worry about it the security of their passwords, using basic words that are all lowercase is completely insecure full stop. -
-
-
CommentAuthorJJenZz
- CommentTimeDec 5th 2007
Okay, thank you muchly for clearing that up and sending me an email to notify me *phew*
-
-
-
CommentAuthorChristopher
- CommentTimeDec 5th 2007
You're more than welcome as it's a perfectly valid question to want answering! -
-
-
CommentAuthorgnome
- CommentTimeDec 5th 2007
I was a bit worried too, because I (being lazy) use the same password in too many spots. -
1 to 6 of 6
