I recently moved my blogs to a dedicated server, however, for reasons unknown to me, Apache2 only lets my blog work if most of the folders are chmodded to 755 (everybody can read, only owner can write, everybody can execute).
Otherwise, the server denies access to the files inside these folders with the error Permission denied: /some/path/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
Google searches returned a huge number of people confronted with the same problem, and who all came to the same conclusion : it only works with 755 permissions.
So, here, I wonder…
Since the recommended file permissions for a folder are 705 (owner and the public – not the group – can read, only owner – neither the group nor the public – can write, owner and the public – not the group – can execute) and not 755, is it really a big deal, please, to have your folders with this extended level of permissions ?
It’s a dedi hosting the blog, and a well-secured one (debian squeeze, suhosin, security modules, each website with his own virtual directory and never the same passwords twice, installed by a professional). I’m getting better at managing this stuff and at server security (accepting to host a website with a hidden bloody trojan already at home, and then fighting day and night to expunge the fucker from my previous shared hosting in which it had contaminated every other website of mine, that made me learn quite a lot about logs parsing, obfuscation, and general security requirements, grrrr), but I don’t know if folders with 755 permissions aren’t creating a new risk…
Thanks if you can tell me your opinion, if it’s tolerable to keep folders with chmod 755 🙂
- The topic ‘Folders with 755 permissions, is that horrible ?’ is closed to new replies.