summaryrefslogtreecommitdiff
path: root/server/other/md5_hashcheck.txt
diff options
context:
space:
mode:
authorAndrei Karas <akaras@inbox.ru>2016-08-20 22:10:03 +0300
committerAndrei Karas <akaras@inbox.ru>2016-08-20 22:10:03 +0300
commit5e9e635515a556bea43dc858e0d7774160b7528a (patch)
tree862a0afa26e539f50028f90392f3ae1c20e3afe8 /server/other/md5_hashcheck.txt
parent9f86b6cbe21f8ca3a1d06b1353f071cf5b23d08b (diff)
downloaddocs-5e9e635515a556bea43dc858e0d7774160b7528a.tar.gz
docs-5e9e635515a556bea43dc858e0d7774160b7528a.tar.bz2
docs-5e9e635515a556bea43dc858e0d7774160b7528a.tar.xz
docs-5e9e635515a556bea43dc858e0d7774160b7528a.zip
Update docs from Hercules.
Diffstat (limited to 'server/other/md5_hashcheck.txt')
-rw-r--r--server/other/md5_hashcheck.txt24
1 files changed, 3 insertions, 21 deletions
diff --git a/server/other/md5_hashcheck.txt b/server/other/md5_hashcheck.txt
index d9064b1..0153938 100644
--- a/server/other/md5_hashcheck.txt
+++ b/server/other/md5_hashcheck.txt
@@ -3,7 +3,7 @@
//===== By: ==================================================
//= Hercules Dev Team
//===== Current Version: =====================================
-//= 20140208
+//= 20160210
//===== Description: =========================================
//= This file outlines the login server's MD5 hash check.
//============================================================
@@ -20,27 +20,9 @@ Please refer to your client diff tool manual for the appropriate patch
tools or diffs it may have similar names.)
The serverside settings for the hash check are located in
-conf/login.conf:
+conf/login/login.conf::login_configuration.permission.hash
-// Client MD5 hash check
-// If turned on, the login server will check if the client's hash matches
-// the value below, and will not connect tampered clients.
-// Note: see doc/md5_hashcheck.txt for more details.
-client_hash_check: off
-
-// Client MD5 hashes
-// The client with the specified hash can be used to log in by players with
-// a group_id equal to or greater than the given value.
-// If you specify 'disabled' as hash, players with a group_id greater than or
-// equal to the given value will be able to log in regardless of hash (and even
-// if their client does not send a hash at all.)
-// Format: group_id, hash
-// Note: see doc/md5_hashcheck.txt for more details.
-client_hash: 0, 113e195e6c051bb1cfb12a644bb084c5
-client_hash: 10, cb1ea78023d337c38e8ba5124e2338ae
-client_hash: 99, disabled
-
-To enable MD5 hash checks, set 'client_hash_check' to 'on' and add one
+To enable MD5 hash checks, set 'client_hash_check' to 'true' and add one
'client_hash' entry for each client you want to use.
The group_id can be any of the groups in conf/groups.conf, and it is
useful in case if you want to allow GMs to use a different client