Thanks, I’ll do that (probably tomorrow, today’s a day off!)
Install Scripts are only designed to be put into the public_html dir, and sub-directories underneath that.
Hmm, that doesn’t seem entirely wise.
After having my server subverted a few weeks ago (due to an uploaded Trojan in a WordPress style, beware!) I’ve been doing a lot of reading about security issues.
One of the pieces of advice that is common to many of the sources is NOT to put your installations within public_html. The reason is simple - the installation contains a lot of executable code that you might not want to be directly called, but more, it likely contains passwords - stored in the clear!
Now, supposedly .htaccess will protect you but in practice this is not iron-clad.
First, there are numerous ways of getting around .htaccess (search for “bypass htaccess” or “htaccess exploit”). Most if not all of these require some other weakness in your system - but as I’ve been discovering, the key to security is “belt and suspenders” - you do not want one weakness to open your system up completely.
Second, writing a correct .htaccess is an arcane art. There’s no guarantee that the creator of the package you have really did it right - but more, the user often end up having to tweak the .htaccess to get your package to work on your installation - and frustrated users have been known to turn off the protections on the .htaccess entirely in order to get past obscure bugs.
By keeping your installation out of public_html, you guarantee that by default the web server cannot see these files. You’re getting rid of a lot of the problems I’ve described above - for no work on the user’s part at all.
Just my $0.02! Thanks for a great system.