Thread: [Opentnl-general] Crash on improper read/write pair
Brought to you by:
mark_frohnmayer,
s_alanet
From: Ivan V. <ivanv@SuperDimension.com> - 2006-04-12 09:45:28
|
Hi. Playing around with MasterServer - Client applications I've found that Server application crashes when it wasn't rebuilt after changes in the Client app. I understand that it is because read/write or pack/unpack didn't match. I saw similar post "Server crash just due to TNL_DEBUG??" but it wasn't answered. The question is - How I can protect my server from hackers attacks in similar cases if they are using modified OpenTNL library? Try{ ... }catch{ conn->disconnect("BAD GUY") }? Thanks in advance, Ivan |
From: Mark F. <ma...@ga...> - 2006-04-12 18:12:51
|
In the release build (TNL_DEBUG off) it should just boot the offending client - in debug it is assumed that you are trying to debug connections, therefore it asserts on pack/unpack mismatches. On 4/12/06, Ivan Vorobeychyk <iv...@su...> wrote: > > Hi. > > Playing around with MasterServer - Client applications I've found that > > Server application crashes when it wasn't rebuilt after changes in the > > Client app. I understand that it is because read/write or pack/unpack > > didn't match. I saw similar post "Server crash just due to TNL_DEBUG??" > > but it wasn't answered. The question is - How I can protect my server > > from hackers attacks in similar cases if they are using modified OpenTNL > library? > > Try{ =85 }catch{ conn->disconnect("BAD GUY") }? > > Thanks in advance, > > Ivan > |