Mandatory information about my setup:
Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 2.5.11
PHP version: 5.5.0
MySQL version: 5.5.32
Host: Apache 2.2.3 CentOS
Admin Tools version: 2.5.5 professional
Description of my issue:
We've been trying any possible way of shielding our sites from SQL injections, and that's why we purchased AdminTools. I read the manual, created a .htaccess file, set the SQLiShield on, and other options, but we're still vulnerable. We've always tried with the simple parameter "?a=select a from b" after our urls to verify it, and they are still accesible. What else could we do to be really shielded? Is it an admintools problem? The server is ours, but we started working with apache very recently, and we don't know where we could change settings to help admintools to make its work. Any help would be great.
Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 2.5.11
PHP version: 5.5.0
MySQL version: 5.5.32
Host: Apache 2.2.3 CentOS
Admin Tools version: 2.5.5 professional
Description of my issue:
We've been trying any possible way of shielding our sites from SQL injections, and that's why we purchased AdminTools. I read the manual, created a .htaccess file, set the SQLiShield on, and other options, but we're still vulnerable. We've always tried with the simple parameter "?a=select a from b" after our urls to verify it, and they are still accesible. What else could we do to be really shielded? Is it an admintools problem? The server is ours, but we started working with apache very recently, and we don't know where we could change settings to help admintools to make its work. Any help would be great.
