*cough* Close port 1433 *cough*
[HELP] How can stop hack of database
08/05/2011 19:21
[Admin]Snuggle#16
08/07/2011 04:10
sondo81#17
Most are the "hacker, or scold so" to go over the php scripts from the websites on the server. most have their root server on the same site as their own. hence the rapid access via sql injection. The password is not the problem because it is indeed in the scripts! The websites are the problem because the least secured. hence the fast access!
08/07/2011 05:48
Bаne#18
Agreed, it is acctualy very very easy to secure both your website and your script.Quote:
Most are the "hacker, or scold so" to go over the php scripts from the websites on the server. most have their root server on the same site as their own. hence the rapid access via sql injection. The password is not the problem because it is indeed in the scripts! The websites are the problem because the least secured. hence the fast access!
@Safe; this thread is still talking about how to stop hacking, and the OP has yet to give us ANY news..
08/08/2011 01:47
sondo81#19
So back to topic.
One problem is that PHP's integers are signed 32-bit on 32-bit systems, which is a problem if you are using unsigned 32-bit ids in the database.
Generally speaking, using prepared statements with PDO is the way to go. However, it's still a good idea to filter incoming data to expected data types.
One problem is that PHP's integers are signed 32-bit on 32-bit systems, which is a problem if you are using unsigned 32-bit ids in the database.
Generally speaking, using prepared statements with PDO is the way to go. However, it's still a good idea to filter incoming data to expected data types.