Dennis
Verified User
Hi Wanener,
Look at this thread: http://www.directadmin.com/forum/showthread.php?t=19644&?
I think you need to build suPHP again to fix this issue.
For your other question. I think PHP-CGI is the best way to run the PHP websites. To make it secure...you install suPHP as well. It will tell every account to use only its "base directory". So every account is "isolated" from the other on the server. With Joomla (or other programs) installs you never need to give the public read-write permissions to a specific directory for e.g. components or other plugin's.
If you run CLI, the user with certain permissions for every website is "apache:apache" and if there is a problem with one of the websites a hacker could get to other websites as well. Still there are enough ways to secure your server a little bit more through firewall settings or settings with "noexec" on the temp dir for example.
Hope this helps.
Regards,
Dennis
Look at this thread: http://www.directadmin.com/forum/showthread.php?t=19644&?
I think you need to build suPHP again to fix this issue.
cd /usr/local/directadmin/custombuild
./build update
./build clean
./build suphp
For your other question. I think PHP-CGI is the best way to run the PHP websites. To make it secure...you install suPHP as well. It will tell every account to use only its "base directory". So every account is "isolated" from the other on the server. With Joomla (or other programs) installs you never need to give the public read-write permissions to a specific directory for e.g. components or other plugin's.
If you run CLI, the user with certain permissions for every website is "apache:apache" and if there is a problem with one of the websites a hacker could get to other websites as well. Still there are enough ways to secure your server a little bit more through firewall settings or settings with "noexec" on the temp dir for example.
Hope this helps.
Regards,
Dennis