Linux Permission Assignments
-
A group with a single user would be the same thing as the user contained within the group, permissions wise...right? I don't see a reason to do this
-
Added layer of security when disabling an account? Since the group gave all permissions, once it's removed even if someone accesses that account they still have no rights?
-
@wirestyle22 said in Linux Permission Assignments:
A group with a single user would be the same thing as the user contained within the group, permissions wise...right? I don't see a reason to do this
Well, my guess is that it is to keep people from granting silly group permissions by accident or default.
-
@wirestyle22 said in Linux Permission Assignments:
Added layer of security when disabling an account? Since the group gave all permissions, once it's removed even if someone accesses that account they still have no rights?
No, that would be the same. It's defaults, I'm pretty sure, that matter.
-
@scottalanmiller said in Linux Permission Assignments:
@wirestyle22 said in Linux Permission Assignments:
Added layer of security when disabling an account? Since the group gave all permissions, once it's removed even if someone accesses that account they still have no rights?
No, that would be the same. It's defaults, I'm pretty sure, that matter.
which is referring to the
world
correct? -
To me a group is a collection of a certain type of user and is then used to streamline permissions to certain resources. EG Instead of giving read permission to Cathy, Joan and Frank, you can just create a group with them in it, and give that group read permission thereby simplifying your job.
I cannot for the life of me think why you would want a single user group with the same name as the user in it. Are there permissions that can only be assigned to a group rather than directly to the user?
What am I missing here?
-
@jrc said in Linux Permission Assignments:
I cannot for the life of me think why you would want a single user group with the same name as the user in it. Are there permissions that can only be assigned to a group rather than directly to the user?
What am I missing here?You're right where I am. I have no idea.
-
Yeah, it seems like an extra step that just complicates and confuses things.
-
They do have a reason to exist, they are called User Private Groups and they are better explained here:
Another explanation:
https://security.ias.edu/how-and-why-user-private-groups-unix -
@wirestyle22 said in Linux Permission Assignments:
@scottalanmiller said in Linux Permission Assignments:
@wirestyle22 said in Linux Permission Assignments:
Added layer of security when disabling an account? Since the group gave all permissions, once it's removed even if someone accesses that account they still have no rights?
No, that would be the same. It's defaults, I'm pretty sure, that matter.
which is referring to the
world
correct?I don't know what you mean. World and groups are not the same at all.
-
@jrc said in Linux Permission Assignments:
To me a group is a collection of a certain type of user and is then used to streamline permissions to certain resources. EG Instead of giving read permission to Cathy, Joan and Frank, you can just create a group with them in it, and give that group read permission thereby simplifying your job.
I cannot for the life of me think why you would want a single user group with the same name as the user in it. Are there permissions that can only be assigned to a group rather than directly to the user?
What am I missing here?
Setgid creates group specific permissions for files in the directory with setgid turned on.
Having a group id also lets you do things like have root own a file and be able to modify it but let apache and only apache read it.
Edit: I see Romo beat me to it with the links. I didn't read them until just now.