First, you need to understand what each “segment” means.
- first triad what the owner can do
- second triad what the group members can do
- third triad what other users can do
Your permission set (-rw-------
) only has permissions on the first triad – the owner of the file – which only has read
and write
permissions.
- read The Read permission refers to a user’s capability to read the contents of the file.
- write The Write permissions refer to a user’s capability to write or modify a file or directory.
- execute The Execute permission affects a user’s capability to execute a file or view the contents of a directory.
Therefore, the owner of the group can read the contents of the file/directory, write to the file/directory, and modify the file/directory.
Under careful file/directory ownership policies, I guess this will be okay – but I wouldn’t count on it. If Apache/Nginx/… doesn’t have ownership of the file, your application won’t work.
This being said, I’d like to raise a few questions;
- Why change the permissions of all files/directories on your server?
- Why set a global permission rule, and not individual to each file/directory?
- What’s the end-goal of this?
I’d take some consideration to Jon T‘s answer
solved File system permissions