From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 Description of problem: When logging into the machine via ssh my secondary groups are not set as reported by the id command. Version-Release number of selected component (if applicable): openssh-server-3.9p1-7 How reproducible: Always Steps to Reproduce: 1. Log in via ssh 2. Type 'id' 3. Only primary group is set, none of secondaries Actual Results: Only the primary group is set. If I type 'id' then I see only my primary group. If I type 'id <me>' then I see all the groups I should be in. Expected Results: My 3 secondary groups should also be set Additional info: This machine was upgraded to FC3 from FC2 via 'yum upgrade'. I have a number of other systems where secondary groups are set as expected. I've tried different versions of pam, with no effect. I do not have console access as the machine is in another country, so I can't try logging in from it to see if it works ok.
This may not be ssh specific, as su also fails to set the secondary groups.
I'm sorry but I cannot reproduce this bug. (Neither for ssh nor for su.) Do you have privilege separation on in the sshd config? What glibc version do you have?
I think I have now resolved the issue via strace's of the su process. When nscd is running, only the primary group is assigned, and when I stop nscd, all works as expected. Next I'll try to figure why nscd is acting up. Feel free to either close this bug or reassign it to nscd.
I have narrowed this down. If I disable group caching (enable-cache no), then secondary groups are not assigned. This is the whole group section from my nscd.conf file. enable-cache group no positive-time-to-live group 3600 negative-time-to-live group 60 suggested-size group 211 check-files group yes persistent group yes shared group yes If I change enable-cache to yes, then secondary groups are assigned correctly. # grep nscd /var/log/rpmpkgs nscd-2.3.4-2.fc3.i386.rpm
http://sources.redhat.com/ml/libc-hacker/2005-02/msg00006.html
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2005-096.html