I am running a COPVPServer and i really ****** of the botters in my server.
I would like to know more about EnigmaProtector because i protected my conquer.exe lately and it can be replace by another so in that case they can use there hacks again.. I would like to know how do you link your Conquer.Exe to your Server(exe). Just like ClassicCo if you replace there exe you cant log on..
One of the methods I've heard thrown around involves the following steps.
A: A launcher which checks the md5hash of your client and launches a silent proxy (so you can check on things from server side)
B: When connecting to account server, the server checks if you're also on the silent proxy. If so it checks the running processes and other things to ensure you're running a legit client and no known hack programs.
There's still plenty of ways to bypass it but if you code everything properly then you'll have a fairly secure setup.
Also.. if you want to bother with a bit of reverse engineering then you could overwrite the encryption in the client with your own. Makes for a ton of work if anyone wants to try to hack on yoru server.
One of the methods I've heard thrown around involves the following steps.
A: A launcher which checks the md5hash of your client and launches a silent proxy (so you can check on things from server side)
B: When connecting to account server, the server checks if you're also on the silent proxy. If so it checks the running processes and other things to ensure you're running a legit client and no known hack programs.
There's still plenty of ways to bypass it but if you code everything properly then you'll have a fairly secure setup.
Also.. if you want to bother with a bit of reverse engineering then you could overwrite the encryption in the client with your own. Makes for a ton of work if anyone wants to try to hack on yoru server.
The problem with a silent proxy is that if it's not done in either a native language or pretty good obfuscated then it would be easy to bypass.
Loaded module checks, spell encryption change & add a layer of encryption to packets.
Ping packets to confirm your AntiCheat is online, if you're creative something I designed last night can actually check if a proxy is in the works with just one packet.
Use something like Themida to protect your anticheat.
As for client modification if your anticheat is solid, you can just chuck that into there and do Server <--> AntiCheat verification
@Pro4Never
Process checks? O.o, why? What if they have a proxy process running thats for a different server.. false positive
The most I've done for blocking cheaters was to inject a DLL which was rewriting all assembly around common known places like wall jump, PM message, etc. So... at the end, edited or not, the executable was useless.
I was changing the cryptographer keys (both COSAC & CORC5). I was changing the WDF hash method. I was changing two constants which are sent to the server, but mostly unknown as they're useless... One was used by the injected DLL to determine if the client was mine, the second was edited by the client to indicate to the MsgServer that the DLL was injected.
Mhm. Else, there were a lot of server-side verification for like revive hack, wall jump, long jump, speed hack, auto-click, etc. All those verifications were direct botjail when detected.
Worked well enough to block most cheats. It wasn't a problem on my servers...
The most I've done for blocking cheaters was to inject a DLL which was rewriting all assembly around common known places like wall jump, PM message, etc. So... at the end, edited or not, the executable was useless.
I was changing the cryptographer keys (both COSAC & CORC5). I was changing the WDF hash method. I was changing two constants which are sent to the server, but mostly unknown as they're useless... One was used by the injected DLL to determine if the client was mine, the second was edited by the client to indicate to the MsgServer that the DLL was injected.
Mhm. Else, there were a lot of server-side verification for like revive hack, wall jump, long jump, speed hack, auto-click, etc. All those verifications were direct botjail when detected.
Worked well enough to block most cheats. It wasn't a problem on my servers...
[HELP] Protecting .eix and .epk files againist unpacking 11/11/2010 - Metin2 Private Server - 13 Replies I know... It's bad section. I'm VERY sorry. But... In Discussions & Questions are so noob questions. This information is very important for me.
I want to protect my files from /pack/ folder. They are very important and I don't want to someone steal it. But I don't know how. I know , that German Servers have that files protected ( Other encryption key in Your packer). Could you tell me how to do it ? Please do not delete this topic. If you want to answer , could You use english ? If you can't...
[HELP] Protecting .eix and .epk files againist unpacking 11/10/2010 - Metin2 Private Server - 1 Replies I want to protect my files from /pack/ folder. They are very important and I don't want to someone steal it. But I don't know how. I know , that German Servers have that files protected ( Other encryption key in Your packer). Could you tell me how to do it ? Please do not delete this topic. If you want to answer , could You use english ? If you can't use english post in German, Maybe I will manage to translate it :)
Protecting your Aion Account from theft 12/31/2009 - Gaming News - EN - 0 Replies With an increase in Aion account thefts being reported, keeping game accounts safe has become a high priority for us all. What can you do to ensure the safety of your own account? NCsoft shares a few tips.
Uzi Guide to protecting ur account (NOOBY Edition) 12/01/2006 - CO2 Guides & Templates - 3 Replies this is realy nooby guide lol so dont flame me thought it be good idea to post this coz everyone post scmming account why not protecting also .....
---------------------------------------->Ackno wledging the Danger<---------------------------------------- -
I've seen many, many situations which people have been hacked, and from four main reasons:
1.) They had a password that was easy to crack.
2.) They were too trusting to the point they let their online spouse, one they've never seen...
AMEN
