Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • stator86 Friend
    #170460

    I followed THESE STEPS in installation process

    I don’t want to change files/folder permissions because, I’m afraid this may harm my site.

    we2solutions Friend
    #423540

    Hi,

    which files/folder you going to give permissions

    please read this.it will give you more explanation

    http://www.ostraining.com/blog/joomla/how-to-change-joomla-folder-and-file-permissions/

    Thanks

    stator86 Friend
    #423541

    Permissions of these folders 755 & files are 644

    However, all of them are unwritable except configuration.php

    administrator/components Unwritable
    administrator/language Unwritable
    administrator/language/ar-AA Unwritable
    administrator/language/en-GB Unwritable
    administrator/language/overrides Unwritable
    administrator/manifests/files Unwritable
    administrator/manifests/libraries Unwritable
    administrator/manifests/packages Unwritable
    administrator/modules Unwritable
    administrator/templates Unwritable
    components Unwritable
    images Unwritable
    images/banners Unwritable
    images/fbfiles Unwritable
    images/sampledata Unwritable
    images/stories Unwritable
    language Unwritable
    language/en-GB Unwritable
    language/overrides Unwritable
    libraries Unwritable
    media Unwritable
    modules Unwritable
    plugins Unwritable
    plugins/authentication Unwritable
    plugins/community Unwritable
    plugins/content Unwritable
    plugins/editors Unwritable
    plugins/editors-xtd Unwritable
    plugins/extension Unwritable
    plugins/search Unwritable
    plugins/system Unwritable
    plugins/user Unwritable
    templates Unwritable
    configuration.php Writable
    cache (Cache Directory) Unwritable
    administrator/cache (Cache Directory) Unwritable
    /home/elib4vet/public_html/theriogenology.net/logs (Log directory) Unwritable
    /home/elib4vet/public_html/theriogenology.net/tmp (Temp directory) Unwritable

    stator86 Friend
    #423544

    I tried several permissions combinations the only 2 work were: 777 & 776

    I think they aren’t save. Is them?

    we2solutions Friend
    #423545

    All files on UNIX (including Linux and other UNIX variants) machines have access permissions. In this way the operating system knows how to deal with requests to access the files. There are three types of access:

    Read – Denoted as r, files with read access can be displayed to the user.
    Write – Denoted as w, files with write access can be modified by the user.
    Execute – Denoted as x, files with execute access can be executed as programs by the user.
    Access types are set for three types of user group:

    User – The owner of the file.
    Group – Other files which are in the same folder or group.
    World – Everyone else.
    The web server needs to be able to read your web pages in order to be able to display them in a browser. The following permissions need to be set in order for your web site to function properly.

    All HTML files and images need to be readable by others. The value for this is 644 (readable by User, Group and World, and writable by User). It is set automatically when you upload files.
    All folders need to be executable by others. The value for this is 755 (readable by User, Group and World, writable by User, executable by User, Group and World). It is set automatically when you create a folder.
    All CGI files (all files in the cgi-bin folder) need to be executable by other. The value for this is 755 (readable by User, Group, and World, writable by User, executable by User, Group, and World). It is not set automatically when you upload files. You need to change file permissions manually.
    It is important that none of your files or folders is writable by anyone else. Any file or folder which is writable by others can be erased by them.

    source from :http://www.siteground.com/tutorials/cpanel/file_permissions.htm

    stator86 Friend
    #423546

    I’ve done these steps. However, the problem still found. Any other solutions?

    stator86 Friend
    #423550

    Here is the solution to aid others may experience same problem

    using SSH

    chown -R nobody.nobody /path to your root directory

    My question here, Does chowning to nobody instead of a user hurt my security?

Viewing 7 posts - 1 through 7 (of 7 total)

This topic contains 7 replies, has 2 voices, and was last updated by  stator86 13 years ago.

We moved to new unified forum. Please post all new support queries in our New Forum