Anyway to protect gunzdb?

[djrox2kool]

title says it all

a mofo like pheonix_147 fucking shithead

[MentaL]

[own_prox]

First clue protect your site first lol

[djrox2kool]

zzz -.- A tutorial on data encryption plz?

Pm me dont give here.

[Phoenix]

Lol you retard, don't jump to conclusions. Your Login.dbo was deleted by someone else. No protection is gonna help you against him XD

[Guy]

Sanitizing data on your registration/login/etc portal scripts is the first step: escape single quotes with another single quote.

Next is preventing XSS/tag injection - the PHP "htmlentites" function should suffice.

Next is protecting the server-end of the bargain; setup DEP to run for all applications, so should an overflow a occur, little to no damage will happen. Setup all incoming data from MDaemon to the database to be sanitized (You could setup a proxy database connection, to find queries and escape them, or setup a procedure to be called at the beginning of all Gunz procedures, for sanitization).

Lastly, keep your Windows box up-to-date, enable Windows firewall, limit the amount of half-open connections (A la registry edits), and run both Gunz and the MSSQL service as limited users.

There go the simplest solutions I have to offer you - enjoy.

[Phoenix]

Gosh you're pro gWX0!

[Rotana]

First of all, dont call people shithead here.

Second, Protect your site with an good anti sql function
And change the table names in the database, so it will be harder to do an sql injection.

[kintukishu]

Ban ke lode phoenix_147 phoenix_147 Mother fker. tere ma ke chuut mei kala bomb


ban ke land ik bare samne to aa

phone number le

or mera le le

09212222322

sale mene pc pe bulaya or tune dhoka deya ban ke land u took my db and delete al lchar

b2o ke burge tere ma to mei chodunga ik bare thoda contact to mil jaye

tuje sab pata chal jayega mother fker zzzz reply kuteya ke aulad

[katsumi]

Ban ke lode phoenix_147 phoenix_147 Mother fker. tere ma ke chuut mei kala bomb


ban ke land ik bare samne to aa

phone number le

or mera le le

09212222322

sale mene pc pe bulaya or tune dhoka deya ban ke land u took my db and delete al lchar

b2o ke burge tere ma to mei chodunga ik bare thoda contact to mil jaye

tuje sab pata chal jayega mother fker zzzz reply kuteya ke aulad

Which language ?
Google translator not able to detect

[Guy]

First of all, dont call people shithead here.

Second, Protect your site with an good anti sql function
And change the table names in the database, so it will be harder to do an sql injection.

Changing the table names won't do anything when you can query for all the table names and columns.

"Protect your site with an good anti sql function"

1) That should be "a good".
2) Preventing SQL injection for MSSQL is as simple as escaping single quotes with another single quote

e.g.

function antisql ( $sql ) {
    return ( str_replace( "'", "''", $sql ) );
}

3) Sanitizing SQL queries won't provide protection for your HTTP daemon; like I said, enable DEP for all applications, run as a limited/jailed user, keep your system up-to-date, lock down policies (A la policy editor, if available), and enable Windows Firewall. All those solutions are free and easy to implement, and not in the slightest way vague - off you go, OP.

[Phoenix]

That kishu bish is such an illiterate arse ._.

[cnatttu]

Which language ?
Google translator not able to detect

Oh hahahahahaha , awsome question :P =)) Phoenix xD


why would you want to translate abuses instead of PRESSING THE REPORT BUTTON ?

btw its an Indian language

[OmgIneedHelp]

Yeh its indian language Phenoiz Ass.. My ha ha ha ha his mom randiii. Dhokebaaj Ban ka land chuteya ka patha mother chood gandu

[Donald Duck]

Changing the table names won't do anything when you can query for all the table names and columns.

"Protect your site with an good anti sql function"

1) That should be "a good".
2) Preventing SQL injection for MSSQL is as simple as escaping single quotes with another single quote

e.g.

function antisql ( $sql ) {
    return ( str_replace( "'", "''", $sql ) );
}

3) Sanitizing SQL queries won't provide protection for your HTTP daemon; like I said, enable DEP for all applications, run as a limited/jailed user, keep your system up-to-date, lock down policies (A la policy editor, if available), and enable Windows Firewall. All those solutions are free and easy to implement, and not in the slightest way vague - off you go, OP.

What he says. You could also hook the MatchServer functions that are doing the query's, then clean them from there on.