will you all know how to get a toribash user password from a computer
you only go to login.dat and open it!
it is unsecure!
so how about making it a little harder!
there is a billion way to encrypt!
example:
md5
ex to md5:
scorpionma=8f38c4ab6f490b609f2aafe113f2e125
toribash=7aef8141831aabe4590819eef635fe52
another examle about encrypting
Hashing Encryption:
ex:apache-htpasswd
toribash:3d5545fb6463546ed6167744eda54464

I support this.
There was a time when i was downloading old versions of the game from other sites and the log in data of the one who uploaded it was still there and still accessible. Though these are responsibilities of the ones who uploaded it, it would somehow lessen the reports on hacked accounts.

If only. Yet another thing we've bugged hampa about to no avail.

You realize md5 is easily decrypted, don't you?

IF you are going to do this, at least use salts.

Back to the thread, this is hilarious.
The only moment when your login and password is used, is when the client joins the server. When you log in, it actually doesn't log you in, it just copies your login and password to the memory.

When you join a server, the client sends a MLOGIN packet. It's composed like that:

mlogin login pass_md5

It sends your login and password, but the password is in MD5! So why not just save the password in md5 already? lol. I've never had such a funny time when reversing an exe.

This holds a valid point. Whenever i forgot my pass i would just open that file to save time. :3

Increasing login safety is sure a good thing

i realize but
80% dont no how i know its easy
maybe someone wants to view it quick
see the login file and then relize it is encrypted then he goes
or maybe a full page of ussuless thing to make the reader get bored or get confused
and that was just an example
i know there is more secure

The problem remains in that the login file, no matter how it's encrypted, is equally vulnerable and valuable to theft in one manner or another.

Also, SkulFuk, when's the last time this has actually been a problem?

2-3 month since the last "widespread" issue from it.