xt0rt:
Be persistent like herpes until they resolve the situation.:bangin:
They seem to be "Herpes" immune!
Here's the latest response received today:
We understand that such issues can be frustrating, but there is no blame being passed, simply the facts of the matter. To clarify, we do not run PHP in the Apache API, we force it to run in the CGI API, and it makes use of a modified version of the suexec CGI wrapper, called phpsuexec. This means any PHP (or CGI) scripts run as your own user, and not the global web server user (called "nobody") that other hosts are known to use. This offers a lot of advantages, but a primary one is better security by allowing users to set their files to chmod 400, 600, 640, 660, 700, 710, 711, 755, etc. depending on the file, and deny any execute, write/modify or even read access to any other users on the system.
The issue still exists in that it's a shared server. However, that said, we still take measures to deny access to things like find, and many modules and paths and directories via security settings to help prevent the majority of exploits. We take it further by implementing such things as mod_security, we have custom firewalls to prevent scripts/users from binding to local ports to listen for connections with a backdoor, etc., or to connect out over non valid ports as well. We have many settings and restrictions, but being how technology is with web servers and it being a shared server environment, there are still means one could use (though limited) to cause issues with another users' site. So, secure scripts and more appropriate permissions are required for you to have a secure environment for your account--this will effectively prevent all issues from other users/scripts. Only if your own scripts are insecure would a problem be present. Thus, any instructions telling you to set any files or directories to be world write/modify are absolutely unneeded and will only pose a risk.
Regards,
Tim Greer
Systems Administrator - HostGator.com, LLC.
This would seem to imply that my scripts are insecure and by extension Zen Cart's. Consequently it's MY fault and not the host!
Zen Cart recommend:
CHMOD 777 for
/cache
/pub
/images
/includes/languages/english/html_includes
/admin/backups
/admin/images/graphs
These to 444 or 644
/includes/configure.php
/admin/includes/configure.php
So how does a new ZC installer square this? By using a reliable and secure host - but Hostgator insist they are! :wacko:
The only one suffering in all of this is muggins here - with a website down and a cartload of problems to resolve to get it back up - regardless of where I take my hosting business.
G