Timeline for Recommended practices regarding Joomla file/directory permissions and ownership on linux systems?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 8, 2016 at 5:26 | comment | added | DeveloperChris | @NeilRobertson I agree with that list but if there is an exploit which is not trapped by that, your last line of defence is to not give write permissions to the web server (apache et al). That's not a joomla specific piece of advice by the way. Also most people cannot implement many of the recommendations in that list. They simply do not have the resources or are using cheaper (not the cheapest) hosting. | |
| Sep 8, 2016 at 3:11 | comment | added | Neil Robertson | Steps 1 to 10 of the "Keeping a Joomla Website Secure" list at joomla.stackexchange.com/a/180/120 together with the standard file permissions has been working fine for the 50 or so websites I've been looking after for the last few years. Your mileage may vary of course. | |
| Sep 8, 2016 at 2:16 | comment | added | DeveloperChris | Yes I know its the "recommended" but once you have been exploited and work out why you were exploited I can assure you you throw the "recommendations" out the window and start from scratch. The recommendations are the path of least resistance. Not the most secure. | |
| Sep 7, 2016 at 11:47 | comment | added | Neil Robertson | Thanks Chris but I'll probably be sticking with the standard 755 and 644 file permissions while this is recommended by the official Joomla website and security experts such as Sucuri: docs.joomla.org/Security_and_Performance_FAQs blog.sucuri.net/2015/09/… | |
| Sep 6, 2016 at 23:11 | review | First posts | |||
| Sep 7, 2016 at 6:57 | |||||
| Sep 6, 2016 at 23:09 | history | answered | DeveloperChris | CC BY-SA 3.0 |