Skip to contentSkip to conversation

setgid - its current use

DISCUSSION Albert Cahalan 2 participants 2 messages Apr 8, 2004 – Apr 9, 2004

lore
Share & tools
lore
#0 lore raw
Quoted 10 lines · Dhruv Gami
Quoted 9 lines · Denis Vlasenko
Quoted 6 lines · Dhruv Gami

I'd like to know the possibility of using setgid for users to switch their groups and work as a member of a particular group. Essentially, if i want one user, who belongs to groups X, Y and Z to create a file as a member of group Y while he's logged on as a member of group X, would it be possible through setgid() ?

Quoted 8 lines
Quoted 1 line

it is possible through chmod

but that would be an explicit way of doing it, right ? I'm looking for doing this via some system calls or something transparent to the user. At most I'd like to query the user for the group as which he wants to work. Which would essentially be a question I ask at login or beginning of a session.

I think you need user-private groups and setgid directories.

First of all, ensure that each user has a group of their own. Do NOT put all users into a "users" group. So user "gami" would be in group "gami", or maybe a "gami_group" group if you prefer. Have the home directories owned by these groups.

Second, set the umask to allow group write access. (this is why you need the user-private groups)

Now suppose you have two users, bill and tom, who need to work together on the spamming project. Create a group called "spamming". Create a project directory /projects/spamming owned by root and in the spamming group. Make this directory setgid and group writable. Any files created in this directory will be owned by the spamming group. Due to the umask setting, permissions on these new files will allow access by all group members. The setgid bit will propagate to any newly created directories, but not to newly created files.

#1 lore raw
Quoted 11 lines

I think you need user-private groups and setgid directories.

First of all, ensure that each user has a group of their own. Do NOT put all users into a "users" group. So user "gami" would be in group "gami", or maybe a "gami_group" group if you prefer. Have the home directories owned by these groups.

Second, set the umask to allow group write access. (this is why you need the user-private groups)

Quoted 12 lines

Now suppose you have two users, bill and tom, who need to work together on the spamming project. Create a group called "spamming". Create a project directory /projects/spamming owned by root and in the spamming group. Make this directory setgid and group writable. Any files created in this directory will be owned by the spamming group. Due to the umask setting, permissions on these new files will allow access by all group members. The setgid bit will propagate to any newly created directories, but not to newly created files.

that must be the fine-grained control _i_ was after!! thank you... and we thought mandrake was a little stupid for doing new users that way... neural oops

Signature · 6 lines
Rob Couto [[email protected]]
Rules for computing success:
1) Attitude is no substitute for competence.
2) Ease of use is no substitute for power.
3) Safety matters; use a static-free hammer.
--