Topic: Simple anticheat
Hello, is it possible to make vanilla server with a simple anticheat that will check the size of the teeworlds.exe, and if it not equal to config number kick player?
You are not logged in. Please login or register.
Teeworlds Forum → Development → Simple anticheat
Hello, is it possible to make vanilla server with a simple anticheat that will check the size of the teeworlds.exe, and if it not equal to config number kick player?
Hello, is it possible to make vanilla server with a simple anticheat that will check the size of the teeworlds.exe, and if it not equal to config number kick player?
Because teeworlds is open source it is easy to create a modified client who will send exactly these information to the server which the server need to receive to believe it is an original file.
And you could not use custom clients anymore, because their size differs, too.
Shikby wrote:Hello, is it possible to make vanilla server with a simple anticheat that will check the size of the teeworlds.exe, and if it not equal to config number kick player?
Because teeworlds is open source it is easy to create a modified client who will send exactly these information to the server which the server need to receive to believe it is an original file.
I know, but i want to make a server+ client for my local proverder's net. I think that there are no people in it who can do it
Shikby, what you are asking is impossible, the server cannot know the size of the teeworlds binaries the client is using. You won't be able to build any anti-cheat protection unless you do something (not reliable) about movements detection, such as the xyz's.
Unless you make your own client and allow it only to connect to your server and make it scan crc scans of the client to your server a checksum. Sending a string to your server and make your server read that string if it does not exsit end connection. Mabey a hardware id send that. Add hooks to SetMousePos and GetMousePos,OpenProcess,FindWindow,to disable client hooking of these functions mainly used by hack creators.If the processes are hooked by a external program then send server info such as hwid,username,ip,hostname. And i would suggest disabling dll injection
http://stackoverflow.com/questions/8693 … -injection
Also search for known hack processes and debuggers through file system and in open procceses and send server what programs are opened and send the server what processes are known and opened and close the client i think this should cover the basics.
Unless you make your own client and allow it only to connect to your server and make it scan crc scans of the client to your server a checksum. Sending a string to your server and make your server read that string if it does not exsit end connection. Mabey a hardware id send that. Add hooks to SetMousePos and GetMousePos,OpenProcess,FindWindow,to disable client hooking of these functions mainly used by hack creators.If the processes are hooked by a external program then send server info such as hwid,username,ip,hostname. And i would suggest disabling dll injection
http://stackoverflow.com/questions/8693 … -injectionAlso search for known hack processes and debuggers through file system and in open procceses and send server what programs are opened and send the server what processes are known and opened and close the client i think this should cover the basics.
Scanning for a crc is the same as said before with the filesize: You wouldn't be able to use modified clients any more.
Disabling the hooks would only prevent extern hacks. Hacks that are build into the client would not be detected.
Disabling dll injection could be possible, don't know how easy it would be, but I think it breaks the K.I.S.S. principle.
And I don't like this anticheat: If you have the game in the background and want to use f.e. cheat engine for cheating in another game, teeworlds would exit even if you don't use cheat engine on teeworlds.
Btw, you can't cheat in teeworlds using any hack programs such as cheat engine or artmoney, as all information like health and ammo are serverside.
-> Anticheat possible, but it would break the K.I.S.S. principle. As it wouldn't be simple anymore. And as teeworlds is opensource you could just remove the anticheat from the client, or let the client always send that everything is ok.
-> Anticheat possible, but it would break the K.I.S.S. principle. As it wouldn't be simple anymore. And as teeworlds is opensource you could just remove the anticheat from the client, or let the client always send that everything is ok.
No it's not possible. Fighting DLL injections may be possible, but then, you will have to deal with the pixel analysers and the man-in-the-middle attacks, which do not use a modified client.
I would suggest making your own driver and hooking everyhing there then what is the client going to do lol. Be able to hook all what u want and disable cheat engine kernel driver. Mabey also add hiding your process.
Could make it for your own mod i guess and just dont release the source code and make only your modifed client connect to your modified server.Fighting Dll injections is 100% possible if you know what your doing. And in cheat engine you can do more than you think.
Merged two posts. /Kottizen
I would suggest making your own driver and hooking everyhing there then what is the client going to do lol. Be able to hook all what u want and disable cheat engine kernel driver. Mabey also add hiding your process.
Could make it for your own mod i guess and just dont release the source code and make only your modifed client connect to your modified server.Fighting Dll injections is 100% possible if you know what your doing. And in cheat engine you can do more than you think.
Merged two posts. /Kottizen
Why not just program our own driver? That does not follow the KISS-prinicple. And why should any serious software do something like that? Your ideas are better for programming a virus but not teeworlds.
What else can you do with CE than memory hacking? Aimbots? Server Crashes? I don't think so.
Teeworlds will always be open source. Not releasing the source code will result that f.e. only people who have windows will be able to play cause they cannot compile the client for Linux.
Teeworlds does not need any dll-injection-protection cause most of all aimbots seem to be coded directly into the client and not by a dll, because this is much more work.
inv0lt wrote:I would suggest making your own driver and hooking everyhing there then what is the client going to do lol. Be able to hook all what u want and disable cheat engine kernel driver. Mabey also add hiding your process.
Could make it for your own mod i guess and just dont release the source code and make only your modifed client connect to your modified server.Fighting Dll injections is 100% possible if you know what your doing. And in cheat engine you can do more than you think.
Merged two posts. /Kottizen
Why not just program our own driver? That does not follow the KISS-prinicple. And why should any serious software do something like that? Your ideas are better for programming a virus but not teeworlds.
What else can you do with CE than memory hacking? Aimbots? Server Crashes? I don't think so.
Teeworlds will always be open source. Not releasing the source code will result that f.e. only people who have windows will be able to play cause they cannot compile the client for Linux.
Teeworlds does not need any dll-injection-protection cause most of all aimbots seem to be coded directly into the client and not by a dll, because this is much more work.
Before thinking to the KISS, think to what is possible. At first, having the project closed source doesn't mean it would only be available on Windows... there are a lot of games (or mods, in this forum) which are closed source but are released on different OS.
Also, for what you are proposing, there is no need to make the whole Teeworlds closed-source, a client and server mod would do the trick. But still, even if you fight dll-injections, there are still several other ways to bypass a client-sided protection.
Teeworlds Forum → Development → Simple anticheat
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.