Disable F11 Button

[dreamer13]

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.

[zTek]

That's actually not a bad idea. However I wouldn't know where to start.

[BaussHacker]

You need to customize the client as you cannot do it through the source.

[Spirited]

Originally Posted by BaussHacker

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.

[BaussHacker]

Originally Posted by Fаng

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.

[Spirited]

Originally Posted by BaussHacker

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. =|

[BaussHacker]

Originally Posted by Fаng

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:

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#)

[Spirited]

Originally Posted by BaussHacker

How would you do it, when you make sure it's always connected to the server?

You could do I like this:

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.

[BaussHacker]

Originally Posted by Fаng

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.

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.

[Korvacs]

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.

[dreamer13]

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

[BaussHacker]

Originally Posted by dreamer13

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.

[_DreadNought_]

Originally Posted by Korvacs

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

[BaussHacker]

Originally Posted by _DreadNought_

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

Make an autopatcher, so you can always update it with modifications fast.

[dreamer13]

can someone help me with this?