Hi Slavko, On Sun, Jun 17, 2012 at 1:19 AM, Slavko <li...@slavino.sk> wrote: > IMO, you must to logout/login to new memberships can be in play :-) > > or use the newgrp command.
Thank you for these suggestions. They do work :) I had a look at the newgrp source code and it does what i expect it to do. newgrp is installed at /usr/bin/ with owner root and setuid bit on. # ls -l `which newgrp` -rwsr-xr-x root root /usr/bin/newgrp This means that it is executed with root permission with any user. In the code, it calls setgid(new_group_name) after routine checking for permissions and prompts for password if necessary. After that it drops its permission to the user who executed this command with setuid(getuid()) and initializes the environment variables if `-' option is given. My point is that there is not some miracle happening here. What happens under the hood that the new memberships don't come into play if I don't logout/login or change the group ID of a login session using `newgrp' ? Is this behaviour expected? I don't think so. After all, /etc/passwd & /etc/group and some other related files are read by the functions in libc to check the permission whenever a user wants to do something, for example change a directory or write to a file or execute a binary, etc. What is it that the new memberships don't come into play immediately? Most importantly, is this behavior desired after all? I would very much appreciate any explanation and answer. Thanks, Vivek -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAENtUgrSbEwmA6U=C4S1HZLMsqLa-_yiz-n=br6h6ds_lnn...@mail.gmail.com
