About "extasis" Hack

[snoopy81]

From posts I read here, I understand this kind of hack consist at connecting a gserver or some other software to the WLserver, suposelly not protected.

So, some questions:
- What's the use of "game-server-list = 192.168.1.1" line(s) in WLserver.cfg. I checked the string "game-server-list" is inside the exe. I didn't took time to experiment further here.
- Wouldn't be really simple to block 2500 port from outside. In a case off multihosting, main hosteur could easelly add 2nd hosteur IP to firewall's "safe-zone".

[tommu00]

"extasis hack" is a "bug" in worldlogserver which lets unauthorized(well wlserver never filtered any incoming connections by ip address) hgserver registrations through by default. hgserver sends registration request to wlserver and wlserver accepts it.

EDIT-->
When there is a map down, or some map (in the target hbserver) then
you just host that map yourself and when you go to that map, you will be moved to your own hgserver.

And yes, you don't need to have a map down to do this, you need modified hgserver(for example gm-commands without admin-level) and some random map name hosted on that server, then (I don't know other ways) fake mainlogserver which you can "log on" to (you host it yourself) and then when you get asked account and password, you type real target account(password can be left black with modified client)), char list pops out(hchar name,exp and level modified via config file), you log in and this "mlserver) sends client the information of your own hgserver, from where you edit your character and then teleport back to some "real" map hosted by the real hoster. (I'll try to get these collected some day in near future, they're kinda scattered atm. and post here)
<--EDIT

Here's little information (and little extra) why 2500 cant simply be blocked:

1.You start hb client

2.You try to log in with acc&pass

3.Client connects to server ip which is written in client's .exe-file and port 2848(mainlogserver)

4.Mainlogserver looks for account you asked and checks the password, then it sends the accounts character content along with character's "what it looks like" which are those apprid-lines in character.txt file (mlserver sends as well the hgserver's ip and port in which resides the map those characters are in so client can log straight to hgserver from login screen)

4.Client chooses character and connects to ip:port which was appointed to it by mlserver

5.Hgserver receives the client's connection request, discusses if it's okay with mlserver and wlserver(correct if i'm wrong) and then the client is "in the game"

6.When client is about to change map, hgserver first looks if the target map is in it's own "hosted maps list", if its not, then if sends client wlservers ip and port(usually 2500)

7.Client connectes to mlserver and asks "tell me which hgserver(ip and port) contains this map i want to log in to", if the map is known hgserver map to wlserver, then wlserver sends the information to client to which the client then connects (to hgserver).


Thus if you block wlserver port from connections coming from "the internet", you will deny client's ability to ask, which map is on which hgserver and then on hgserver-map change, client gets disconnected But it can log back in to the map it changed to.

[RageIlluminati]

Thus if you block wlserver port from connections coming from "the internet", you will deny client's ability to ask, which map is on which hgserver and then on hgserver-map change, client gets disconnected But it can log back in to the map it changed to.

so.. there is no anti-hack against this shit? I mean yeahh if you have a source.. you can program it into it.. but with "china" files you can't to a shit?

[shreX]

Bah, in sql files u cant download chars and edit these, u can only steal cfgs... cfgs without serverfiles is crap.

[snoopy81]

Bah, in sql files u cant download chars and edit these, u can only steal cfgs... cfgs without serverfiles is crap.

Maybe, but if you can get the character as a Stream, you can still save the stream, modify then send it back....

[Jaap]

Thus if you block wlserver port from connections coming from "the internet", you will deny client's ability to ask, which map is on which hgserver and then on hgserver-map change, client gets disconnected But it can log back in to the map it changed to.

Not true. The client asks this to the Mainlogserver, not the Worldlogserver...

The client NEVER connects to the Worldlogserver, therefor you can block the port. Make sure you don't block the port for any external hosters, as each HGserver needs a connection to the Worldserver.

[RageIlluminati]

Thus if you block wlserver port from connections coming from "the internet", you will deny client's ability to ask, which map is on which hgserver and then on hgserver-map change, client gets disconnected But it can log back in to the map it changed to.

Not true. The client asks this to the Mainlogserver, not the Worldlogserver...

The client NEVER connects to the Worldlogserver, therefor you can block the port. Make sure you don't block the port for any external hosters, as each HGserver needs a connection to the Worldserver.

emm... wierd.. If I blocked 2500 port.. I mean I promised only connections to 2500 port from my own comp external IP 64.231.22.***.. then all player got this DC problem when they changed HGserver... what could be wrong?

I use HBchina files.. with MSSQL

[Dax]

The client does connect to the worldlogserver when it changes map. Blocking that port will cause a DC each time you switch HGs.

EDIT: Woah i really must start reading entire topics or atleast more than the last post. My post was already covered Oh well, I blame society, it's always society's fault.

[tommu00]

The client asks this to the Mainlogserver, not the Worldlogserver...
The client NEVER connects to the Worldlogserver, therefor you can block the port.

Someone has not been doing his/her homework correctly How then you could explain in such detail those things client discusses with MLServer o_O *wonders*

mlserver(port involving player): 2848 (usually)
wlserver(port involving player): 2500 (usually)

[Jaap]

Wow interesting, this makes life so much easier! Tnx
No more guessing for the port number! Yay

[locobans]

Wow interesting, this makes life so much easier! Tnx
No more guessing for the port number! Yay

Outpost is a growing comunity, everyone is learning here B)

[snoopy81]

Hum tested tommu00 anti-Extasis-hack, but the hack still get trough...
Something wrong I guess, but nevermind, releasing this hack, and precise explanations, is great to help us protect our servers... ty