| Because the apache server runs as a user called, say, 'www', any files which are owned by the user 'www' will be writable by any rogue php script, cgi file, whatever. Since there is a HUGE amount of bad code out there, imagine if you download and install a product, and a bug is discovered in it. That application can then overwrite your website. Let me tell you from experience, waking up in the morning and finding out that your website has been transformed into a militant extremist propaganda site is *VERY* upsetting. So your first line of defense against this is to assure that *NO FILES* are owned by, or writable by, the apache user. There are, of course, exceptions to this - like when you *need* Apache to be able to write to a specific file or directory. On Jul 29, 2010, at 1:06 PM, James Godrej wrote:
|
|