Why You Should Never Use 777 Permissions Anywhere, Ever, Full Stop, End of Story
The assigned permissions for a file determine who can read, write and execute the file or directory. The first number is for the owner of the file, the second the group and the third "everyone else." The numerical value is arrived as follows:
1 is execute
2 is write
4 is read
Adding them together is how the permissions for the file or directory are determined. Full permissions add up to 7 (4 + 2 + 1 = 7.)
Thus, 777 permissions allow the following:
Read Write Execute for Owner
Read Write Execute for Group
Read Write Execute for Others
Yes, but what does it mean?
With 777 permissions, you are giving anyone with an internet connection full access to the files or directories with those permissions. They may alter them in any way they choose, including maliciously. Many account hacking incidents stem from 777 permissions.
At Black Chicken Host, we recognize the severity of the threat from 777 permissions, and our servers are configured to reject access to them by default. It is not possible to change this behavior to work with 777 files and/or directories. Instead, you will need to set your files to 644 and your folders to 755, which are appropriate permissions.
We're happy to help you find ways around 777 permissions in our server environments! Typically, setting 644/755 permissions does the trick, but if not, just send up a flare via support ticket and let us know the following:
- The full path to the file or folder in question
- The troubles you're having with it
- The exact text of the error you're seeing
Was this answer helpful?
This article only applies to VPS and Dedicated customers - Shared account holders do not have...
Running PHP scripts within the cron environment can be fraught with peril and frustrations if...
PHP directives may be enabled and disabled in a custom php.ini file located in your home...
For enhanced security, Black Chicken Host uses an suPHP environment. suPHP allows PHP and HTML...