GreenBox Posted September 10, 2012 Share Posted September 10, 2012 As of r16771, the login-server can perform a server-side check of the client MD5 hash, ensuring that the client was not tampered. The client only send the correct MD5 hash on certain server types/server types so a diff is needed to ensures that it will send the hash, for this you can use this WeeDiffGen plugin. Check conf/login_athena.conf for instruction on how to enable it. 11 Link to comment Share on other sites More sharing options...
randell1993 Posted September 10, 2012 Share Posted September 10, 2012 This is awesome btw ^^ will be much much more better if there would be a plugin for the diff to check the hash of grf too ^^ Link to comment Share on other sites More sharing options...
Euphy Posted September 10, 2012 Share Posted September 10, 2012 Great work! Link to comment Share on other sites More sharing options...
EvilPuncker Posted September 10, 2012 Share Posted September 10, 2012 This is awesome btw ^^ will be much much more better if there would be a plugin for the diff to check the hash of grf too ^^ indeed Link to comment Share on other sites More sharing options...
GreenBox Posted September 10, 2012 Author Share Posted September 10, 2012 The diff just forces the client to send the hash in all servicetypes, it's an already existing code. Checking GRF hash would be much more complex. 1 Link to comment Share on other sites More sharing options...
shatowolf Posted September 11, 2012 Share Posted September 11, 2012 Great news! thanks man. Link to comment Share on other sites More sharing options...
clydelion Posted September 11, 2012 Share Posted September 11, 2012 Very nice!! This is great in conjunction with HackShield! My suggestion is to use battle_config.client_hash_check instead, so it can be reloaded via @reloadbattleconf, thus a restart is not required when changing clients. 1 Link to comment Share on other sites More sharing options...
Brian Posted September 11, 2012 Share Posted September 11, 2012 ^ but it's the login-server checking, and I think battle_config is only stored in the map-server's RAM. Link to comment Share on other sites More sharing options...
xazax Posted September 11, 2012 Share Posted September 11, 2012 And you only need to restart the login server. 1 Link to comment Share on other sites More sharing options...
Napster Posted September 11, 2012 Share Posted September 11, 2012 When setting enable // Client MD5 hash check // Check client hash? client_hash_check: yes Char Server Can't connect to Login server Show Wrong password s1/p1 Link to comment Share on other sites More sharing options...
GreenBox Posted September 11, 2012 Author Share Posted September 11, 2012 Fixed at r16775 Link to comment Share on other sites More sharing options...
JulioCF Posted September 11, 2012 Share Posted September 11, 2012 very nice! thanks Link to comment Share on other sites More sharing options...
Rebel Posted September 12, 2012 Share Posted September 12, 2012 Ahmm.. I tried using it but i cant connect.. It says "Your Game's Exe File is not the latest version." Link to comment Share on other sites More sharing options...
mleo1 Posted September 14, 2012 Share Posted September 14, 2012 Very nice!! This is great in conjunction with HackShield! My suggestion is to use battle_config.client_hash_check instead, so it can be reloaded via @reloadbattleconf, thus a restart is not required when changing clients. how do you reneme the client and make it workable with hackshield? I heard it only works when the client's name is 'RagRE.exe' Link to comment Share on other sites More sharing options...
akihito Posted September 16, 2012 Share Posted September 16, 2012 wow pretty nice changes +1 Link to comment Share on other sites More sharing options...
Antares Posted September 18, 2012 Share Posted September 18, 2012 Sounds nice. Does this mean that players can't use alternative (hacked) clients and bot clients (ok) anymore if you enable it? Link to comment Share on other sites More sharing options...
PewN Posted September 18, 2012 Share Posted September 18, 2012 (edited) is this also block open kore? can u help me about this? how can i set it to the hash? oops. my pass Edited September 18, 2012 by bVersatile Link to comment Share on other sites More sharing options...
malufett Posted September 18, 2012 Share Posted September 18, 2012 is this also block open kore? IMO..for now yes..but once they add a new function to support sending of modified Hash code to server..well that's a hole.. Link to comment Share on other sites More sharing options...
PewN Posted September 18, 2012 Share Posted September 18, 2012 (edited) is this also block open kore? IMO..for now yes..but once they add a new function to support sending of modified Hash code to server..well that's a hole.. can u help me i don't know how to config it ~.~ check my post is this working on 2010-07-30 Client? cuz other client have bug on wrong password i want to make it on 2010-07-30 please!! @GreenBox. Please support 2010-07-30 client's on the md5 hash Edited September 18, 2012 by bVersatile Link to comment Share on other sites More sharing options...
Vianna Posted September 20, 2012 Share Posted September 20, 2012 is this also block open kore? IMO..for now yes..but once they add a new function to support sending of modified Hash code to server..well that's a hole.. They already do, and it's been a while since it had been implemented. It's still undocumented, though. *coughs* clientHash *cough* servers.txt ~ Link to comment Share on other sites More sharing options...
Aries Posted September 20, 2012 Share Posted September 20, 2012 Lovely Link to comment Share on other sites More sharing options...
Brynner Posted September 20, 2012 Share Posted September 20, 2012 how can i change the client MD5 Hash Check?for example i just want to make my own client_hash Link to comment Share on other sites More sharing options...
GreenBox Posted September 20, 2012 Author Share Posted September 20, 2012 I didn't understood what you want, sorry ._. Link to comment Share on other sites More sharing options...
kyeme Posted September 20, 2012 Share Posted September 20, 2012 is this also block open kore? IMO..for now yes..but once they add a new function to support sending of modified Hash code to server..well that's a hole.. can u help me i don't know how to config it ~.~ check my post is this working on 2010-07-30 Client? cuz other client have bug on wrong password i want to make it on 2010-07-30 please!! @GreenBox. Please support 2010-07-30 client's on the md5 hash +1 Please support this on 2010-07-30 client please Link to comment Share on other sites More sharing options...
Brynner Posted September 20, 2012 Share Posted September 20, 2012 I didn't understood what you want, sorry ._. is it possible to make my own client hash?for example. i just made my custom client hash. so once the other user cannot connect on my server if they use other version of client even if they add the diff for implementation of md5hash Link to comment Share on other sites More sharing options...
