From ef439f32648f3e9eca0c4f3b69413b53891cf3e7 Mon Sep 17 00:00:00 2001 From: ultramage Date: Sat, 28 Apr 2007 14:34:58 +0000 Subject: * Tried and fixed md5 password encryption - login_sql was doing stupid things like re-using one pre-generated key for all connections, and escaping binary md5 data (destroying it) - added missing code to login_txt when creating new accounts, showing that storing passwords as md5 hashes never really worked for txt - removed PASSWORDENC's conditional compilation effect, now just a flag - greatly simplified md5 password checking code, credits to eapp * login server will now bind only after finishing the init phase git-svn-id: https://rathena.svn.sourceforge.net/svnroot/rathena/trunk@10384 54d463be-8e91-2dee-dedb-b68131a5f0ec --- conf-tmpl/login_athena.conf | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'conf-tmpl') diff --git a/conf-tmpl/login_athena.conf b/conf-tmpl/login_athena.conf index 39d87ebc9..3ad980de6 100644 --- a/conf-tmpl/login_athena.conf +++ b/conf-tmpl/login_athena.conf @@ -163,7 +163,8 @@ check_client_version: no // What version we would allow to connect? (if the options above is enabled..) client_version_to_connect: 20 -// Passwords in Login DB are MD5 - cannot b used on client with this on +// Store passwords as MD5 hashes instead of plaintext ? +// NOTE: Will not work with clients that use use_MD5_passwords: no // Ipban features (SQL only) -- cgit v1.2.3-70-g09d2