Patching The Server Crasher For Servers.

To "not get hacked" by server crashers and Kore, change you're matchserver port. Remember, it's hexdecimal.
Contact me for help at ; nova@legendgamers.org


Thanks for reading.

-Nova

Wizkidje said on LG forums that u don't have any scripten expierence. I trust you. But did you created this?

Lol. Wizkid sais allot. Want prof I patched it ?

EDIT,
I evan patched Kore...

Checking for malformed packets doesn't seem that impressive..

Quote:

---

Originally Posted by gWX0

Checking for malformed packets doesn't seem that impressive..

---

Hihi, Nothing is.

Quote:

---

Originally Posted by Nova™

Hihi, Nothing is.

---

Well, according to Jacob, it would appear you just changed the port matchserver runs on..

The inherit problems in that are self-explanitory. This is no "patch".

Me: sry u didn't patch it
Him:Yarly
Him:ANd you're planning
Him :to finde the port of evrey matchserver you use
Me: *netstat -n

It's what it is and it stopt the bot from getting in - now if you're going to spend time looking for the port that's you're own probleme.

Quote:

---

Originally Posted by Nova™

It's what it is and it stopt the bot from getting in - now if you're going to spend time looking for the port that's you're own probleme.

---

No, that doesn't stop it - if you would setup a sniffer to check for what packet is being sent, you would be capable of noticing the specific byte couplet being responsible for the crashing of the MDaemon.

To find the port:

1) Run the client, connect, and use a networking tool to view active connections (As Phail stated, netstat with the "-n" argument works fine).

2) Disassemble the client, check the arguments for connecting to the server (Including port).

3) Check any number of other client files responsible for storing the connection port of the server.


All in all, it would take a matter of seconds to "update" the crasher.

Like I said, check UDP port that's relative to 6000 and you got it, rofl, or hook connect() and you got it.

Quote:

---

Originally Posted by gWX0

No, that doesn't stop it - if you would setup a sniffer to check for what packet is being sent, you would be capable of noticing the specific byte couplet being responsible for the crashing of the MDaemon.

To find the port:

1) Run the client, connect, and use a networking tool to view active connections (As Phail stated, netstat with the "-n" argument works fine).

2) Disassemble the client, check the arguments for connecting to the server (Including port).

3) Check any number of other client files responsible for storing the connection port of the server.


All in all, it would take a matter of seconds to "update" the crasher.

---

Cause it's true. 100% of users at this forum know how to do that. Don't they.

Quote:

---

Originally Posted by Nova™

Cause it's true. 100% of users at this forum know how to do that. Don't they.

---

It doesn't matter if no one at this community isn't aware - it only takes one developer from any other community.

Hello then.
It's a noob attempt. That's all lol;

Quote:

---

Originally Posted by Nova™

Hello then.
It's a noob attempt. That's all lol;

---

Then why are you attempting to make money off your "noob attempt"?

cause hes lazy and cant get a real job?