summaryrefslogtreecommitdiff
path: root/doc/md5_hashcheck.txt
diff options
context:
space:
mode:
authoreuphyy <euphyy@54d463be-8e91-2dee-dedb-b68131a5f0ec>2012-09-21 20:36:34 +0000
committereuphyy <euphyy@54d463be-8e91-2dee-dedb-b68131a5f0ec>2012-09-21 20:36:34 +0000
commitfb4775c97532aa931de381a51518edee037f9c8e (patch)
treec6d77b7f633ed28c78f6334f746114b46855e51a /doc/md5_hashcheck.txt
parent5bf76cb12ca9f7ba06f2856e512917e20d9a95f6 (diff)
downloadhercules-fb4775c97532aa931de381a51518edee037f9c8e.tar.gz
hercules-fb4775c97532aa931de381a51518edee037f9c8e.tar.bz2
hercules-fb4775c97532aa931de381a51518edee037f9c8e.tar.xz
hercules-fb4775c97532aa931de381a51518edee037f9c8e.zip
* Merged eAthena ea:15187 by ai4rei, effect list improvements (doc\effect_list.txt)
* Follow-up r16787, revised documentation and comments on MD5 hash check * Added svn:eol-style=native property on some recent files git-svn-id: https://rathena.svn.sourceforge.net/svnroot/rathena/trunk@16788 54d463be-8e91-2dee-dedb-b68131a5f0ec
Diffstat (limited to 'doc/md5_hashcheck.txt')
-rw-r--r--doc/md5_hashcheck.txt82
1 files changed, 38 insertions, 44 deletions
diff --git a/doc/md5_hashcheck.txt b/doc/md5_hashcheck.txt
index 13cda2bb9..9c2f3b8b5 100644
--- a/doc/md5_hashcheck.txt
+++ b/doc/md5_hashcheck.txt
@@ -1,44 +1,38 @@
-//===== rAthena Documentation ================================
-//= Login Server's MD5 Hash Check
-//===== By: ==================================================
-//= rAthena Dev Team
-//===== Current Version: =====================================
-//= 20120921
-//===== Description: =========================================
-//= This file outlines how the built-in MD5 Hash Check is
-//= used and steps enable it.
-//============================================================
-
-In revision r16771, the login server received an update that allows it to perform
-a server-side check of the client to find out it's MD5 hash. This update is an
-effort towards ensuring that a user has either:
-a.) not been tampered with the client
-b.) using the client specific to that particular server
-
-At present, we know that the client can only send the correct MD5 hash to the server
-when using particular server types, so a diff is required to ensure that any client
-can send the hash. A link to the required diff plugin for WeeDiffGen can be found at:
-http://rathena.org/board/topic/70841-r16771-client-md5-hash-check/
-
-Check conf/login_athena.conf for instruction on how to enable it.
-
-In conf/login_athena.conf you will find the following:
-// Client MD5 hash check
-// Check client hash?
-client_hash_check: off
-
-This setting simply accepts on or off.
-
-
-// Put your client hashes here, a player can login into the server using
-// a hash with a group_id equal or lower the account group_id
-// Format: group_id, hash
-// Examples:
-client_hash: 0, 113e195e6c051bb1cfb12a644bb084c5
-client_hash: 99, cb1ea78023d337c38e8ba5124e2338ae
-
-Once enabled, you would use those lines to configure this feature (or even as an example).
-The group_id can be any of the groups in conf/groups.conf and can be particularly useful
-if, for example, you wanted to restrict normal players from dual-clienting and use a lower
-number for chat flooding, but wanted to allow dual-clienting and 255 lines before the chat
-flood kicks in for your GMs. \ No newline at end of file
+//===== rAthena Documentation ================================
+//= MD5 Hash Check
+//===== By: ==================================================
+//= rAthena Dev Team
+//===== Current Version: =====================================
+//= 20120921
+//===== Description: =========================================
+//= This file outlines the login server's MD5 hash check.
+//============================================================
+
+The login server is able to perform a check of the client's MD5 hash.
+This will ensure that a user has not tampered with the client and that
+the client is the one specific to your server.
+
+The client can only send the correct MD5 hash to the server on certain
+server types, so a client diff is required to ensure the hash is sent.
+A link containing the required WeeDiffGen plugin can be found at:
+http://rathena.org/board/topic/70841-r16771-client-md5-hash-check/
+
+The settings for the hash check are located in conf\login_athena.conf:
+
+// 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
+// A player can login with a client hash at or below the account group_id.
+// Format: group_id, hash
+client_hash: 0, 113e195e6c051bb1cfb12a644bb084c5
+client_hash: 99, cb1ea78023d337c38e8ba5124e2338ae
+
+To enable MD5 hash checks, set 'client_hash_check' to 'on'.
+The 'client_hash' group_id can be any of the groups in conf\groups.conf,
+and is particularly useful if you wanted to allow GMs a different client
+than normal players; for example, a GM client could be hexed differently
+with dual-clienting enabled and chat flood disabled. \ No newline at end of file