![]() Anything uploaded through a browser interface will end up being owned by the webserver process (or its alias) - that includes modules etc. ![]() Like I said, your mileage will vary with the host. Secure your environment first - 'secure' scripts running in an INSECURE environment will give you more problems than 'vulnerable' scripts in a SECURE environment. Lastly, keep one eye open for security issues with the CMS or extensions that you've installed - but don't get paranoid. As your confidence increases, shell out a few bucks for a VPS with root access - you'll be glad you did. You'll soon pick up on a few one-shot commands which will make your life easier. get a hosting account that gives you some level of shell access. Never, EVER, set the x-bit on files (unless it is a shell script or similar) so, no odd numbers on files. ![]() If that is the only way that you can work, then please remember to secure the folders/files again afterwards. The installer sees things from the point of view of the webserver process, but since you FTP'd the files in, then they are owned by the FTP user, so are unwriteable to the webserver process, and you will probably find that you end up opening up permissions to get things to work, which can lead to unhappy situations such as 777/666. You will find that the webserver process generally runs under the alias of 'apache', '700 on folders and 600 on files. In the case of a scenario such as running a website, it follows that the owner of the filesystem should be the webserver process itself, as it runs with very low privileges, can be contained within its own little area, and even if it did escape it can't do much harm. Ideally, file ownership is granted to a user with the lowest privileges (but who is still up to the job). File ownership is one of the hardest concepts for folks to grasp, and your mileage will vary according to the freedoms granted by your hosting company. I run Linux servers for a living, and here's my take on all this. Warning: Cannot modify header information - headers already sent by (output started at /data01/mark/public_html/installation/index.php:23) in /data01/mark/public_html/installation/common.php on line 20.Warning: Cannot modify header information - headers already sent by (output started at /data01/mark/public_html/installation/index.php:23) in /data01/mark/public_html/installation/common.php on line 19.Warning: rename(./configuration.php./oldconfiguration.php) : Permission denied in /data01/mark/public_html/installation/index.php on line 23.I tried lower directory permissions but continued getting "unwritable" errors in the install checker.Īnd for reasons I'm not clear on, I'm still getting the following errors in the installer (will search the forums for these later.): I'm not really happy with 777 on all my directories so if it's possible to use something less open post-installation, it would be great to know. I've now used the following to get the installer to be happy: everything in the Directory and File Permissions Check unwritable (unexpected).configuration.php unwritable (as expected).I took the advice above but got a number of problems from the install checker including: I'm just moving from IIS to Linux and ran into this for the first time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |