New answers tagged mysql
If you want to hard your system you can also fail2ban. It's a script that watch log files and set blocking rules to the firewall in case of illegal access. I use it to monitoring and block the access to not available websites and the ssh login trails. It's easy to configure, without attracting attention and works fine :-)
First of all: create a user to run your PHP code as who has no more user rights than needed, including being jailed within his user context configure suphp get a hardening guide for ubuntu and follow it thoroughly configure apparmor limit user access and have a remote logging tool set up implement auditd for sensitive folders set up SSL with a valid ...
The primary reason not to use AES_* functions in MySQL is because they are using ECB block mode of operation, which is insecure. Read more at: https://en.wikipedia.org/wiki/Block_cipher_mode_of_operation
(I disagree that it's a duplicate of Is it preferable to perform encryption using database functions or code? although there is a lot of overlap) The only justification I can think of for the post - and it is an important and valid one - is that it's easy to scale the application tier (PHP) but hard to scale a relational database tier (MySQL). For the ...
There is no particular standard for what parameterised queries look like, so it could just as well be any syntax. I'm not sure what DB layer you were previously using that preferred %s (but if it's the Python MySQLdb then the reason for that is that it's using its own non-native parameterisation function which actually uses the string format operator to drop ...
Spoofing. When the actual services go down, attacker tries to spoof as if he's the service provider and starts collecting secret information. For example, within an enterprise network, one could DoS a DNS server and start dummy instance of DNS (with same ip, but probably different MAC -- even same MAC sometimes by spoofing) and wrongly resolving the domain ...
Top 50 recent answers are included