Hey,
Have you looked at the /etc/nsswitch.conf
Example of what you should see.
You may want to consider using sudo. That is what we use at my job. It is installed by default on RHEL. It will give select users admin/root power. This what you wanted right?
You might also want to switch to LDAP. We are making a move from NIS to LDAP.LDAP has more features and is more secure.
Hello anyone... I am new to UNIX and I recently bought a Sparc 10 to play around with. Well, last night I executed something called EasyInstall in my /usr/etc/install directory and I selected to "Use NIS". Now when my system boots up it is looking for a NIS server to connect to and keep trying(... (5 Replies)
Hello all,
I'm not sure if this is the right forum, but I would like to know if Redhat running NIS ( not NIS +) would have conflict with Solaris running NIS+. Currently I am running NIS+ on Solaris but will be adding RedHat to the network. I seem to be unable to find and information regarding... (2 Replies)
Hi all,
I just took over the admin role from someone and I wanna setup sendmail (just to send mail from the host) however, after I config all the resolv.conf, nssitch.conf, hosts file and when I try to send a mail out, after I punched ctl-D, it returned he following,
"NIS map mail.aliases... (2 Replies)
We have a RedHat 8.0 NIS master, with a RedHat 8.0 NIS Slave.
We also have a small number of SUSE 9.1 and SUSE 10 machines here for evaluation.
However, no matter what i do, the SUSE machines will not talk to the NIS Servers.
If i broadcast for NIS Servers for the specified NIS domain, it... (1 Reply)
Hi Guys,
I have lots of doubts regarding NIS+.I also think by basics could be wrong......I am trying to pick up stuff from documents which are a bit murky. I am working on production environment so I am afraid of trial and error! Please help.
1) What is the difference between root domain master... (1 Reply)
Hi, all.
I have a Solaris client here needs to bind to NIS server in another subnet. Following is the configuration i made on the client,
1) edit /etc/inet/hosts to add an entry of the NIS server -- nserver01
2) execute `domainname` to set local NIS domain to the domain of the NIS server.... (1 Reply)
I'm creating a scrip for auditing our AIX box's to ensure that they are built according to our system standards. I'm not sure on the logic for checking to see if the NIS and NIS+ services are disabled. any idea's? (2 Replies)
Discussion started by: sport
2 Replies
LEARN ABOUT SUNOS
yppasswd
yppasswd(1) User Commands yppasswd(1)NAME
yppasswd - change your network password in the NIS database
SYNOPSIS
yppasswd [username]
DESCRIPTION
The yppasswd utility changes the network password associated with the user username in the Network Information Service (NIS) database. If
the user has done a keylogin(1), and a publickey/secretkey pair exists for the user in the NIS publickey.byname map, yppasswd also re-
encrypts the secretkey with the new password. The NIS password may be different from the local one on your own machine.
yppasswd prompts for the old NIS password, and then for the new one. You must type in the old password correctly for the change to take
effect. The new password must be typed twice, to forestall mistakes.
New passwords must be at least four characters long, if they use a sufficiently rich alphabet, and at least six characters long if mono-
case. These rules are relaxed if you are insistent enough. Only the owner of the name or the super-user may change a password; superuser on
the root master will not be prompted for the old password, and does not need to follow password construction requirements.
The NIS password daemon, rpc.yppasswdd must be running on your NIS server in order for the new password to take effect.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWnisu |
+-----------------------------+-----------------------------+
SEE ALSO keylogin(1), login(1), nis+(1), nispasswd(1), passwd(1), getpwnam(3C), getspnam(3C), secure_rpc(3NSL), nsswitch.conf(4), attributes(5)WARNINGS
Even after the user has successfully changed his or her password using this command, the subsequent login(1) using the new password will be
successful only if the user's password and shadow information is obtained from NIS. See getpwnam(3C), getspnam(3C), and nsswitch.conf(4).
NOTES
The use of yppasswd is discouraged, as it is now only a wrapper around the passwd(1) command, which should be used instead. Using passwd(1)
with the -r nis option (see nis+(1)) will achieve the same results, and will be consistent across all the different name services avail-
able.
BUGS
The update protocol passes all the information to the server in one RPC call, without ever looking at it. Thus, if you type your old pass-
word incorrectly, you will not be notified until after you have entered your new password.
SunOS 5.10 28 Nov 2001 yppasswd(1)