Disable F11 Button

Page 1 of 2 1 2
07/21/2011 04:20 dreamer13#1
Can SomeOne Help Me Disable The F11 Button, Or Make It So When You Use It Is Disconnects You, For Project X Source Or 5165 Source.
07/21/2011 04:29 zTek#2
That's actually not a bad idea. However I wouldn't know where to start.
07/21/2011 05:08 BaussHacker#3
You need to customize the client as you cannot do it through the source.
07/21/2011 07:36 Spirited#4
Quote:
Originally Posted by BaussHacker View Post
You need to customize the client as you cannot do it through the source.
Even if you could- people can hack conquer.exe so it doesn't function.
07/21/2011 07:38 BaussHacker#5
Quote:
Originally Posted by Fаng View Post
Even if you could- people can hack conquer.exe so it doesn't function.
That's why you do it off the conquer process. Ex. running another executeable, that should always have connection with the server somehow, to make sure it's not closed.
07/21/2011 07:40 Spirited#6
Quote:
Originally Posted by BaussHacker View Post
That's why you do it off the conquer process. Ex. running another executeable, that should always have connection with the server somehow, to make sure it's not closed.
Even I could kill that though or replicate it. It's still not a good idea. =|
07/21/2011 07:43 BaussHacker#7
Quote:
Originally Posted by Fаng View Post
Even I could kill that though or replicate it. It's still not a good idea. =|
How would you do it, when you make sure it's always connected to the server?

You could do I like this:
Code:
Executable -> Data -> High Encryption -> Send -> Server 2 -> Valid? -> Executable -> Conquer -> Kill
No ways, you can replace it, without cracking it. Of course obfuscate or use a crypter. In cases of peoples wanting to crack it. (Depending on, if it's coded in C#)
07/21/2011 07:51 Spirited#8
Quote:
Originally Posted by BaussHacker View Post
How would you do it, when you make sure it's always connected to the server?

You could do I like this:
Code:
Executable -> Data -> High Encryption -> Send -> Server 2 -> Valid? -> Executable -> Conquer -> Kill
No ways, you can replace it, without cracking it. Of course obfuscate or use a crypter. In cases of peoples wanting to crack it. (Depending on, if it's coded in C#)
Well... people figured out the new cryptography by cracking conquer.exe. So... anything is possible. I would just rely on other checks in the server. This isn't reliable.
07/21/2011 07:57 BaussHacker#9
Quote:
Originally Posted by Fаng View Post
Well... people figured out the new cryptography by cracking conquer.exe. So... anything is possible. I would just rely on other checks in the server. This isn't reliable.
The chances are small.

Code:
Executable -> Encryption 1 -> Server -> Decryption 1
Server -> Encryption 2 -> Executable -> Decryption 2
Use custom encryption and not public once.
And any security is better than nothing.

Of course nothing is impossible to crack.
07/21/2011 09:44 Korvacs#10
The problem with doing it on a separate application is that in actual fact you dont add a second layer of security at all, its vulnerable to the same attack that the conquer client is, just inject into the application and by-pass the encryption.
07/22/2011 20:45 dreamer13#11
you cant make it so when you press it, it just d/c you cause in project x they make it so when you use aimbot commands you disconnect o.o
07/22/2011 20:52 BaussHacker#12
Quote:
Originally Posted by dreamer13 View Post
you cant make it so when you press it, it just d/c you cause in project x they make it so when you use aimbot commands you disconnect o.o
We even made an external processor check, but never finished it and even if we did, then I wasn't going to make it public as it's the same I'm using atm. Just highly modified etc. Anyways, you can, but I'm afraid there is no help at such areas. When it comes to security you must be on your own.
07/22/2011 21:19 _DreadNought_#13
Quote:
Originally Posted by Korvacs View Post
The problem with doing it on a separate application is that in actual fact you dont add a second layer of security at all, its vulnerable to the same attack that the conquer client is, just inject into the application and by-pass the encryption.
1. Make it a dll, Just adds the extra flavor.
2. Add checks to packets that only the injector can do(Such as checksums encrypted)
3. Encryption, Heavy heavy encryptions!
4. Bind the exe and dll
5. Or skip step 4 and hide it.
6. Have packets send THRU the conquer connection(hooks) to make sure its running.
7. Repeat step 1-6 x2 then step 7 three times.

If they can break that, That theres no point trying to keep them away :rolleyes:
07/22/2011 21:50 BaussHacker#14
Quote:
Originally Posted by _DreadNought_ View Post
1. Make it a dll, Just adds the extra flavor.
2. Add checks to packets that only the injector can do(Such as checksums encrypted)
3. Encryption, Heavy heavy encryptions!
4. Bind the exe and dll
5. Or skip step 4 and hide it.
6. Have packets send THRU the conquer connection(hooks) to make sure its running.
7. Repeat step 1-6 x2 then step 7 three times.

If they can break that, That theres no point trying to keep them away :rolleyes:
Make an autopatcher, so you can always update it with modifications fast.
07/22/2011 22:00 dreamer13#15
can someone help me with this?
Page 1 of 2 1 2