1847895 Members
3501 Online
104021 Solutions
New Discussion

OpenSSH and groups

 
SOLVED
Go to solution
Elmar P. Kolkman
Honored Contributor

OpenSSH and groups

We have a openssh setup here, but for some reason when you login using it, only the primary group is set correctly for the user. The result is that if the user is member of more then one group, he can't access files belonging to its other groups.

Anyone knows if there is an option (configuration or compiletime if there isn't a configuration option) to solve this?
Every problem has at least one solution. Only some solutions are harder to find.
4 REPLIES 4
Steven E. Protter
Exalted Contributor

Re: OpenSSH and groups

pwck
# checks the /etc/passwd file
grpck
# checks the /etc/group file

Also state your version number.

I'm using HP's port of openssh Secure Shell 3.6.1 p2 and am not experienceing this problem.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Elmar P. Kolkman
Honored Contributor

Re: OpenSSH and groups

pwck gives some warnings on non-existent homedirectories and non-alpha character as first character of the login name.

grpck gave some warnings on logins that don't exist, so they have been cleaned up, but it didn't solve the issue.

Ssh versions: 3.7.1p2 for both the daemon and client.
Every problem has at least one solution. Only some solutions are harder to find.
Jeff Schussele
Honored Contributor
Solution

Re: OpenSSH and groups

Hi Elmar,

I don't believe this is abnormal. The users need to use the
newgrp grp_name
command to effectively change their group.
Have them use the
id
command before & after to see the change.

Alternative is to use the /etc/logingroup so that they won't have to use newgrp. Do a
man group
for further details.

HTH,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Elmar P. Kolkman
Honored Contributor

Re: OpenSSH and groups

Thanx. You gave me the golden hint: /etc/logingroup didn't exist!
Making it a symbolic link to /etc/group solved the problem.
Every problem has at least one solution. Only some solutions are harder to find.