[Idea] Response Server

@syntex ur right but i think not that he wanna release his source!

i think he wanna help us, to improve skills =P
and i hope that he only tell then how it works not the source, i mean by tell how he solved it to bypass the newest hackshield but not step by step tutorial because we wanna learn it

that leechers not only download it, they need to work to understand what Thiesius tell us then ^^

Quote:

Originally Posted by RunzelEier leeching is not just about not giving thanks. its about wanting evering served. 99% of the kal section wants to make 2clicks and then it should work. and if it doesn't work they start whining.

gife haxx blzzz!

Quote:

Originally Posted by MoepMeep gife haxx blzzz!

here you are.
100% working and 100% undetected by hackshield
[Only registered and activated users can see links. Click Here To Register...]

I'm looking for few trustful guys which would be interested in closed beta test of Response Server.

Yesterday I got some time and mood so I started working on the idea mentioned in first post.
What's done:
-> Response Server:
a) Request processing algorithm works fine
b) Basic error check
c) Should work asynchronously

-> Interactor:
(Took much less time to write than I imagined)
a) Kills hackshield
b) Capable of loading selected dll files in kalonline folder. So we don't have to use injector or write proxy loading routines and bypasses.
c) Manages data transfer between engine and Communicator

-> Communicator:
a) Handles data received from Interactor (engine) and sends it to Response Server
b) Does basic error check
c) Returns correct response to game executable

What needs to be done:
a) Communicator executable implemented in interactor DLL -> So it will load on dll start up
b) Couple other minor things
This shouldn't take much time but I don't fancy finishing it at the moment.

How are you going to use it?
Simple:
Proxy of dbghelp serves us as Interactor.
Communicator will be loaded from the Interactor.

Benefit for me:
The goal is testing asynchronous mechanism of Response Server (Which will be rewritten anyways).

Benefit for you
You will be able use debugger, cheat engines (even the plain one), trainers (EagleNT is not loaded), old/new hooks and detours.
Basically the process acts like it wouldn't be protected by HackShield.

Don't spam crap, thanks.

#First quick test
hehepwnz pointed out issue: The response server at this moment uses executable and memory dump of New UI. The old UI isn't compatible with HackShield message mechanism (leading to expel).

Interesting... I thought more people would use this opportunity to get something for themselves. Like base pointers or just to play around with debugger. You can still "sign up". I can't test asynchronous algorithm with 4-5 people (I could simulate the tests but I would rather test it "on-line").

Last update
The communicator was implemented into Interactor dll (Needs some touchings - Doesn't support multi-client atm.).

<-----too newb to even test, you know...

It's not matter of skill. 90% people are able to copy a dll.
However I redesigned some elements of the Interactor. I think I could make the open-beta soon.

mkay then count me in.... ^^

That is some pretty awesome stuff, I've had some programming/networking classes so it all makes sense but i could never do that... and then i joined the military so its pretty much all lost since i haven't used in a few years. I'm just glad theres still some life in this section back when i first came here it was my inspiration to learn all the networking/programming but i could never benefit the community so i just kinda left checking back once in a while.

Now im leaving the service and going back to school maybe i can learn some more advanced things than i did in highschool to actually help out around here (hate being a leech but ill help you test it if you don't get people with more credibility)

Again nice work and keep it up :handsdown:

There will be a little break for moment.
I need to redesign some stuff.

Also some problem around 13. request appeared (discovered by MoepMeep), leading into expel. The request wasn't however anyhow special. Standard memory CRC request.
I created fresh memory dump of engine. However I will have to also sniff all the packets around the 13. request to see if there isn't some engine "InixStyle" check.
Don't know if I will have time to do it in upcoming days...
(1 hour really isn't enough)

After the fixes and analysis the server will be recompiled to run on Linux and moved to different machine.

Trying to get my sendsniff working without any crashes, so I can do this for you.

The Response Server is almost ready to go for Open Beta.
What's been changed:
ResponseServer:
- Won't be placed on Linux (I'm too lazy to rewrite a code)
Communicator:
- Rewritten
- Not a part of Interactor anymore
- Multiclient: Should be capable handling up to 25 clients (Should be enough but I haven't tested that)
Interactor:
- Redesigned and rewritten from scratch
- Why to load HackShield at all? Let's replace EhSvc with our interactor and act like a hackshield -> Requires 500% less code than proxy dll
- Needs some touchings in message handling algorithm (Nothing much)

So: Prepare yourself for massive INT "pwning" soon

Last update before open beta:

ResponseServer
- Code is now compatible with Linux
- HackShieldEmulator tweaked
Communicator
- Fixed fatal bug with looping I/O (Though it's only temporary solution)
Interactor
- Nothing changed

Are there any features you would like to have in the Interactor? -> Only mechanics -> no bots or familiar stuff.

Current features:
- Well, no HackShield at all (That should be major feature :D)
- You can specify loading of external dll
(LoadLibrary[0] = myHack_0.dll
LoadLibrary[1] = myHack_1.dll
LoadLibrary[n] = myHack_n.dll)

autopick and joining to nearest party which have free slot, thanks

@pamz12,spanyy idiots.

Good work, I should turn skype on more often :p