[Johnson_boy]

Quote:

Originally Posted by Mauzen Having a moderate protection for the passwords of your users is important, sure. But is it really THAT important in case of samp, to have the most complex and most secure hashing methods, slowing down the server itself and making it more complicated to use? I claim that any sha or whirlpool will be good enough. It might be breakable with brute force, but seriously, wheres the point in dehashing for weeks or months, just to get the password of some samp server account? Its not about money or private information, the worst thing one could do with that is like banning all users. The hacker kids that would try to "hack" into some admin account will just lose interest after some days, and the serious guys simply arent stupid enough to waste their time with samp account hacking. So just like the fear of deamx, I think that actually noone ever dehashed a password for samp (feel free to prove me the opposite). Its way more important to keep the database itself safe. Once someone got access to the database, he can do quite all of the same bad stuff, without needing to crack any passwords. If noone can access the passwords, they wouldnt even have to be hashed (except for privacy of course)

I'm more concerned about the users' privacy than data loss on the SA-MP server. It is a fact that (too) many people use same passwords on many websites and services, including SA-MP. That's why it's vital to keep the passwords safe even though the data on the SA-MP server is not that important.

And of course it is important to keep the database safe, but there is always a chance that an intruder gains access to the data. There's not way to be 100% safe.