Solution against Crash

Its just unpacked 374 main? Why u post it here?
Change client version and magic key does not make us safe...
I just wondering if i would share main like x30 do, i mean launcher -> load empty cabalmain -> cabalmain load main dll's :fanny:
it can protect probably most of hacks, but i dont know how about crash ;>
Maybe in futhure x30 gonna tell us how he figured it out.

On this cabalmain.exe not work channel crasher.

- - - Updated - - -

if lock server only for this cabalmaine.exe u have not problem with crasher :ott1:

Maybe tell us what did u change in it? When i just back to home i gonna try it.

I do not see any reason to convince you to use this cabalmain.exe
I saw that you are interested in the question how to protect yourself from this attack.
I gave you a solution how I see working and simple.
The difference of this exe and those that you have is that there is no anti-cheat system (X-Trap's face it, it just do not need, at least on my server with Ukrainian Russian players where every third person a cheater and gets banned. And they do this cheat is not a hindrance at all, even a child of 10 years old)))
And the main difference (for some reason does not work crasher):
Other addresses in cabalmain.exe and when crasher want add to them the values ​​it fails and nothing happens, it does not even see it.
Later i will do a detailed guide for beginners who have little understanding of how a server can fight back from my decision.)

xor key, magickey and client version is the easiest thing in the world to discover, this is not the most appropriate solution.

The only solution to fix the crash problem is to modify the bins.There is no other way.

Quote:

---

Originally Posted by oOSpikeOo

The only solution to fix the crash problem is to modify the bins.There is no other way.

---

There's a client side fix..

People can crash your channels without a client too. They just need to send you the bad packet and your channel is down :)

Quote:

---

Originally Posted by cadena

clear
service iptables stop
IPTABLE="/sbin/iptables"


$IPTABLE -F
$IPTABLE -Z
$IPTABLE -X


#Cabal Secure Ports
#DBAgent ,GlobalMgrSvr,AuthDBAgent,RockAndRollITS,EventDBAgent
#CashDBAgent ,PCBangDBAgent,EventMgrSvr,GlobalDBAgent,PartySvr
SecPorts="32080,38190,38181,37110,38171,38180,38170,38201,38140,32001"


#Cabal Open Ports
lPort="38101" #LoginSvr Port
cPort="38121" #ChatNode Port
aPort="38151" #AgentShop Port
#WorldSvr Ports
Port1="38111"
Port2="38112"
Port3="38113"
Port4="38114"
Port5="38115"
Port6="38116"
Port7="38117"


$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp -m multiport --dports $SecPorts -j DROP
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $lPort -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $cPort -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $aPort -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $Port1 -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $Port2 -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $Port3 -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $Port4 -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $Port5 -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $Port6 -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
$IPTABLE -A INPUT ! -s 127.0.0.1 -p tcp --dport $Port7 -m string --hex-string '|0000e2b7|' --algo bm -j REJECT --reject-with tcp-reset
service iptables save
service iptables start

---

That script is not really helpful, can still crash channel using crash tool.

Quote:

---

Originally Posted by TriEdge

People can crash your channels without a client too. They just need to send you the bad packet and your channel is down :)

---

If you are talking about direct packet sending without cabalmain.exe, then I guess the iptables script above can block it.

Quote:

---

Originally Posted by Drav3n

That script is not really helpful, can still crash channel using crash tool.

---

Yes.. because crashtool.exe manipulate the enter channel opcode..

I have here a chatnode bad opcode that can crash worldsvr and I test it using the crashtool method of manipulating and sadly its working.. :'(

Worldsvr > baotou bytes to change it, perfect to solve collision, don't need to do other, worldsvr > bytes, this has been solved, but no one is released! Believe that will be released soon! We work together
:thumbup1:

Quote:

---

Originally Posted by 124782692

Worldsvr > baotou bytes to change it, perfect to solve collision, don't need to do other, worldsvr > bytes, this has been solved, but no one is released! Believe that will be released soon! We work together
:thumbup1:

---

can you share something?

edit WorldSvr.bin

Quote:

---

Originally Posted by GODSKIN

edit WorldSvr.bin

---

can you give me some hex address?

MOVEAX ？ Send instructions? 0A 00
Modified to 0F 00?