diff options
| author | Haru <haru@dotalux.com> | 2016-02-11 00:41:54 +0100 |
|---|---|---|
| committer | Haru <haru@dotalux.com> | 2016-08-19 21:32:15 +0200 |
| commit | f56264d23d9cc86a87331401496e206639cdd6e3 (patch) | |
| tree | 57891c2901c8cdc114baf4fbfa4dd927b5a87204 /doc/md5_hashcheck.txt | |
| parent | 3c84a4df688a63577236d02b4d972775964f71ca (diff) | |
| download | hercules-f56264d23d9cc86a87331401496e206639cdd6e3.tar.gz hercules-f56264d23d9cc86a87331401496e206639cdd6e3.tar.bz2 hercules-f56264d23d9cc86a87331401496e206639cdd6e3.tar.xz hercules-f56264d23d9cc86a87331401496e206639cdd6e3.zip | |
Ported login-server.conf to libconfig
Ported to modern Hercules and cleaned up from Panikon's commits: ceb8a486ac47c2ed9aae4baa1ec39a11f31e9368, c1049123a4ea6ae6f0992ffe766db8aed7435ab5, 6feb097046355610d2288670a569ccc175358580, 9f6e27a96d655f2b4555310786d9d10898754404, 21fa5d24255ba026f96b1dbedf74ac5ef831d3ae, e22a56ad4def8ca22e94d44377a5364b9db1a425, f753a754923140bfec02057c16e6e8429b863d0e, 25dde7e46524ace330b83cb4bf0255cc4d796792
Signed-off-by: Haru <haru@dotalux.com>
Diffstat (limited to 'doc/md5_hashcheck.txt')
| -rw-r--r-- | doc/md5_hashcheck.txt | 24 |
1 files changed, 3 insertions, 21 deletions
diff --git a/doc/md5_hashcheck.txt b/doc/md5_hashcheck.txt index d9064b1ab..b386559b5 100644 --- a/doc/md5_hashcheck.txt +++ b/doc/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.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 |