09-21-2016
Thanks for sharing the solution!
I wonder if there is a bug in the libc.
The gid -> gname order should be identical with the gname -> gid order, regardless which method (+: entry or nsswitch.conf) is used.
10 More Discussions You Might Find Interesting
1. HP-UX
HI,
We are facing a problem while trying to login using ssh.
The user is able to login using telnet.
We are able to login as another user using ssh and then su to that user which is successfull.
What should i be checking for the user to be able to login directly using ssh.
Thanks in... (2 Replies)
Discussion started by: sag71155
2 Replies
2. Shell Programming and Scripting
I want to login to server using ssh or telnet and execute one command then exit to the shell
Please let me know how to write script for this? (1 Reply)
Discussion started by: svenkatareddy
1 Replies
3. UNIX for Dummies Questions & Answers
1)
ssh a@b
echo $USER it display the correct value as a (even though i have not defined it in .profile)
2)
remsh b -l a
echo $USER it does not display the value as a (variable is not set
any idea why $USER variable is not initialized when i login via remsh or rlogin but shows the... (10 Replies)
Discussion started by: reldb
10 Replies
4. Shell Programming and Scripting
Hey guys,
I have some task from my office to lock user on the specified directory after the user logged on using ssh. And then run prompt program to fill the required information. Yeah, just like an ATM system.
My question:
How could I do those?? AFAIK I have to edit the ~./bashrc. But the... (1 Reply)
Discussion started by: franzramadhan
1 Replies
5. HP-UX
Hi,
I want to suppress ssh login logs of a particular user to get logged in /var/adm/syslog/syslog.log
As am using a user to monitor a server over ssh in 5 miute interval..and that creating un-necessary logs in my syslog.log file .. Please help me if there any way I can suppress this logs only... (6 Replies)
Discussion started by: Shirishlnx
6 Replies
6. Shell Programming and Scripting
This is a weird problem. Following is my code.
/opt/quest/bin/vastool configure pam sshd
/opt/quest/bin/vastool configure pam ssh
cat /etc/pam.conf | \
awk '$1=="ssh"||$1=="sshd"||$1=="emagent"{sub("prohibit","aix",$NF);}1' OFS='\t' > /etc/pam.conf
cat /etc/ssh/sshd_config | \
sed -e... (2 Replies)
Discussion started by: pjeedu2247
2 Replies
7. Red Hat
I have been asked to see if we can restrict SFTP access to authorised users only. There will be business users who will log on with SSH, but they are locked into a menu. They will have write access to the production data to do their job, but we don't want them to have access to read/write the... (8 Replies)
Discussion started by: rbatte1
8 Replies
8. Solaris
HI Community.
I was trying to create ssh password less authentication for one user called night and it's not working for me.
These are the steps I followed:-
I have logged into the server and issued ssh-ketgen -t rsabash-3.2$ ssh-keygen -t rsa
Generating public/private rsa key pair.... (4 Replies)
Discussion started by: bentech4u
4 Replies
9. UNIX for Advanced & Expert Users
Hello Gurus,
I want One user to su to another without allowing root access and password.
I want to run a specific command as below from user am663:
---------------------------------------------------------
sudo -u appsprj4 /home/appsrj4/scripts/start_apache.sh
-------------------
But... (6 Replies)
Discussion started by: pokhraj_d
6 Replies
10. UNIX for Advanced & Expert Users
I have a user account configuration with ssh public/private key that works on multiple servers centos and rhel. One server (Server F) that is not working in centos 6.8. When i ssh into server f I get prompted for a password. I have verified the config and it all is good. I put sshd into debug... (8 Replies)
Discussion started by: bash_in_my_head
8 Replies
GROUP(5) BSD File Formats Manual GROUP(5)
NAME
group -- format of the group permissions file
DESCRIPTION
The group file /etc/group is the local source of group information. It can be used in conjunction with the Hesiod domain 'group', and the
NIS maps 'group.byname' and 'group.bygid', as controlled by nsswitch.conf(5).
The group file consists of newline separated ASCII records, usually one per group, containing four colon ':' separated fields. Each line has
the form:
group:passwd:gid:[member[,member]...]
These fields are as follows:
group Name of the group.
passwd Group's encrypted password.
gid The group's decimal ID.
member Group members.
The group field is the group name used for granting file access to users who are members of the group.
The gid field is the number associated with the group name. They should both be unique across the system (and often across a group of sys-
tems) since they control file access.
The passwd field is an optional encrypted password. This field is rarely used and an asterisk is normally placed in it rather than leaving
it blank.
The member field contains the names of users granted the privileges of group. The member names are separated by commas without spaces or
newlines. A user is automatically in a group if that group was specified in their /etc/passwd entry and does not need to be added to that
group in the /etc/group file.
Very large groups can be accommodated over multiple lines by specifying the same group name in all of them; other than this, each line has an
identical format to that described above. This can be necessary to avoid the record's length limit, which is currently set to 1024 charac-
ters. Note that the limit can be queried through sysconf(3) by using the _SC_GETGR_R_SIZE_MAX parameter. For example:
biggrp:*:1000:user001,user002,user003,...,user099,user100
biggrp:*:1000:user101,user102,user103,...
The group with the name ``wheel'' has a special meaning to the su(1) command: if it exists and has any members, only users listed in that
group are allowed to su to ``root''.
HESIOD SUPPORT
If 'dns' is specified for the 'group' database in nsswitch.conf(5), then group lookups occur from the 'group' Hesiod domain.
NIS SUPPORT
If 'nis' is specified for the 'group' database in nsswitch.conf(5), then group lookups occur from the 'group.byname' and 'group.bygid' NIS
map.
COMPAT SUPPORT
If 'compat' is specified for the 'group' database, and either 'dns' or 'nis' is specified for the 'group_compat' database in
nsswitch.conf(5), then the group file may also contain lines of the format
+name:*::
which causes the specified group to be included from the 'group' Hesiod domain or the 'group.byname' NIS map (respectively).
If no group name is specified, or the plus sign (``+'') appears alone on line, all groups are included from the Hesiod domain or the NIS map.
Hesiod or NIS compat references may appear anywhere in the file, but the single plus sign (``+'') form should be on the last line, for his-
torical reasons. Only the first group with a specific name encountered, whether in the group file itself, or included via Hesiod or NIS,
will be used.
FILES
/etc/group
SEE ALSO
newgrp(1), passwd(1), su(1), setgroups(2), crypt(3), initgroups(3), nsswitch.conf(5), passwd(5), yp(8)
HISTORY
A group file format appeared in Version 6 AT&T UNIX.
The NIS file format first appeared in SunOS.
The Hesiod support first appeared in NetBSD 1.4.
BUGS
The passwd(1) command does not change the group passwords.
BSD
June 21, 2007 BSD