Re: Where is the problem ?
Disallow any entry and access to your database via GM accounts, external methods (setting your ODBC server option as private, instead of public), unravel the ends of your connection(s) (like managing portforwarding for server, ftp, billingserver, etc), and the list goes on.
Just get some intel about how things do work. You are running a pServer for 7 years, thus you should already have a fix for this kind of problem, though.
Re: Where is the problem ?
Quote:
Originally Posted by
blapanda
Disallow any entry and access to your database via GM accounts, external methods (setting your ODBC server option as private, instead of public), unravel the ends of your connection(s) (like managing portforwarding for server, ftp, billingserver, etc), and the list goes on.
Just get some intel about how things do work. You are running a pServer for 7 years, thus you should already have a fix for this kind of problem, though.
I tried everything :(
Re: Where is the problem ?
First of all clean your host by fully scanning it or reinstall or w/e
cuz even an sql injection could lead to throwing a backdoor into your server!!!
if you're using a filter:
1_try to look into packets that are related to ingame chat/msg that are
going to be stored in sql. you should be cautious about it.
here's an example for it
2_there was an exploit that kept secret for a long time that player
can execute queries through fortress messages. and there is a fix for it
in case of none of them works then it's just your website mate.
try to disable web panel as a temp solution till you check up your entire website