2009-09-01, 03:47 AM
Well, disabling whispers or any other kind of "game options" don't work because of client-server design.
Q1: What happens when you send a private message (whisper)?
A: 1- The message go from your client to Nexon Servers;
A: 2- Nexon Servers ask the destiny client if he is accepting private messages;
A: 2.1- Yes, he accept: show message;
A: 2.2- No, he don't accept: tell the sender: he don't accept.
Q2: So, why disabling whispers don't work?
A: Because there's a problem in Q1 item 2: ask the destiny client. Nexon servers is constantly asking if you're accepting or not accepting, and it is knocking on your client to get answer. D/C Hackers do it using "packet editing" repeating the same message thing over and over flooding your client, make the CPU usage going crazy and disabling Nexon Server to keep other functions like: updating your position, updating your screen to show the people around you, show smegas, and etc.
Q3: Why this design?
A: Because its easy and cheap to implement, and doing so, Nexon avoid too many database reading.
Q4: What do you mean by database reading?
A: Lets create our own D/C hack solution. Imagine we put at Nexon database an new field called: "Accept_Whispers". So next time someone send you a message it gona be like that:
1- client send a private message to Nexon Server
2- Nexon server check in the "Accept_Whispers" field if the desired person is currently accepting whispers;
2.1- If Yes: show;
2.2 If No: tell the sender: desired person not accepting;
Now Nexon Server aren't knocking our client for a answer. And its gona protect us from massive questioning and, maybe, preventing the d/c or lag. But this solution will create massive amounts of database reading and memory allocation to temporary store the messaging waiting for its destiny and cpu usage. Why? Image thousands of clients asking Nexon Servers about person "game options" several times.
The currently design, that allows us to get D/C/Lag hacked, is because Nexon servers work only like a repeater or delivering messages, without doing any database read/write but allowing massive amount of information going too fast (in this case pay attention, i am talking about the "game option" or whisper problem, not the overall game, that contains several different functions to communicate with your client).
What Nexon needs is a good team of network security experts, new routers that allows complex filtering/pattern rules to prevent us from being D/C/Lag hacked. But theres goes another problem: its a four or more million users game, and people currently getting d/c hacked are HT squads teams/leaders, PB squad teams/leaders, merchanting like the guy who started this thread, and several others. But if you compare with the overall users "playing peacefully", doing their 4h 2xCards, chatting, have fun in several ways, the "overall" game works quite perfectly, so a solution to this problem may take some time.
NOTE: That's my opinion, I am not a security expert, but currently working with network development, and I am just guessing the design/behavior. So if I said something stupid, feel free to point me my mistakes. And sorry about my poor/bad grammar english.
Q1: What happens when you send a private message (whisper)?
A: 1- The message go from your client to Nexon Servers;
A: 2- Nexon Servers ask the destiny client if he is accepting private messages;
A: 2.1- Yes, he accept: show message;
A: 2.2- No, he don't accept: tell the sender: he don't accept.
Q2: So, why disabling whispers don't work?
A: Because there's a problem in Q1 item 2: ask the destiny client. Nexon servers is constantly asking if you're accepting or not accepting, and it is knocking on your client to get answer. D/C Hackers do it using "packet editing" repeating the same message thing over and over flooding your client, make the CPU usage going crazy and disabling Nexon Server to keep other functions like: updating your position, updating your screen to show the people around you, show smegas, and etc.
Q3: Why this design?
A: Because its easy and cheap to implement, and doing so, Nexon avoid too many database reading.
Q4: What do you mean by database reading?
A: Lets create our own D/C hack solution. Imagine we put at Nexon database an new field called: "Accept_Whispers". So next time someone send you a message it gona be like that:
1- client send a private message to Nexon Server
2- Nexon server check in the "Accept_Whispers" field if the desired person is currently accepting whispers;
2.1- If Yes: show;
2.2 If No: tell the sender: desired person not accepting;
Now Nexon Server aren't knocking our client for a answer. And its gona protect us from massive questioning and, maybe, preventing the d/c or lag. But this solution will create massive amounts of database reading and memory allocation to temporary store the messaging waiting for its destiny and cpu usage. Why? Image thousands of clients asking Nexon Servers about person "game options" several times.
The currently design, that allows us to get D/C/Lag hacked, is because Nexon servers work only like a repeater or delivering messages, without doing any database read/write but allowing massive amount of information going too fast (in this case pay attention, i am talking about the "game option" or whisper problem, not the overall game, that contains several different functions to communicate with your client).
What Nexon needs is a good team of network security experts, new routers that allows complex filtering/pattern rules to prevent us from being D/C/Lag hacked. But theres goes another problem: its a four or more million users game, and people currently getting d/c hacked are HT squads teams/leaders, PB squad teams/leaders, merchanting like the guy who started this thread, and several others. But if you compare with the overall users "playing peacefully", doing their 4h 2xCards, chatting, have fun in several ways, the "overall" game works quite perfectly, so a solution to this problem may take some time.
NOTE: That's my opinion, I am not a security expert, but currently working with network development, and I am just guessing the design/behavior. So if I said something stupid, feel free to point me my mistakes. And sorry about my poor/bad grammar english.