d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
bacda65d14
freebsd-dev/usr.bin/passwd/passwd.c

244 lines
5.6 KiB
C
Raw Normal View History

BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
/*
* Copyright (c) 1988, 1993, 1994
* The Regents of the University of California. All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. All advertising materials mentioning features or use of this software
* must display the following acknowledgement:
* This product includes software developed by the University of
* California, Berkeley and its contributors.
* 4. Neither the name of the University nor the names of its contributors
* may be used to endorse or promote products derived from this software
* without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*/
#ifndef lint
1) Fix local_passwd to co-operate with dual-personality crypt(3). Changing a local passwd will now keep the encryption type that was originally used to encrypt the password, so folks adding DES to their systems will not be irritated/confused by having MD5'ed passwords in their master.passwd. Coming later is an option to allow the user to choose the encryption type. 2) Fix a bunch of compiler warnings announced by turning on -Wall. I did not get them all, that will come a bit later.
1995-12-16 09:45:17 +00:00
static const char copyright[] =
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
"@(#) Copyright (c) 1988, 1993, 1994\n\
The Regents of the University of California. All rights reserved.\n";
#endif /* not lint */
#ifndef lint
Cosmetic in usage string and err() messages.
1997-07-31 06:57:47 +00:00
#if 0
static char sccsid[] = "@(#)passwd.c 8.3 (Berkeley) 4/2/94";
#endif
Update for new kpasswd interface.
1995-01-20 22:03:36 +00:00
static const char rcsid[] =
Ifdefed conditionally-unused variables.
1998-03-23 14:14:24 +00:00
"$Id: passwd.c,v 1.13 1997/07/31 06:57:47 charnier Exp $";
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
#endif /* not lint */
#include <err.h>
#include <errno.h>
#include <stdio.h>
#include <stdlib.h>
1) Fix local_passwd to co-operate with dual-personality crypt(3). Changing a local passwd will now keep the encryption type that was originally used to encrypt the password, so folks adding DES to their systems will not be irritated/confused by having MD5'ed passwords in their master.passwd. Coming later is an option to allow the user to choose the encryption type. 2) Fix a bunch of compiler warnings announced by turning on -Wall. I did not get them all, that will come a bit later.
1995-12-16 09:45:17 +00:00
#include <string.h>
Cosmetic in usage string and err() messages.
1997-07-31 06:57:47 +00:00
#include <unistd.h>
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
#ifdef YP
#include <pwd.h>
Bug fix: use the use_yp() function in the chpass(1) code to determine correctly whether a user is local or NIS (or both, or neither). If you have a user that exists locally but not in NIS, passwd(1) could get confused and try to submit the password change to NIS. (Fortunately, yppasswdd is smart enough to spot the error and reject the change.) Bug reported by: Charles Owens <owensc@enc.edu>
1995-09-02 04:02:28 +00:00
#include <pw_yp.h>
Merge in changes to support the new rpc.yppasswdd(8) and fix a few bugs. In passwd(1): - Gut most of yp_passwd.c and leave only a few things that aren't common to pw_yp.c. - Add support for -d and -h flags to select domains and NIS server hosts to use when updating NIS passwords. This allows passwd(1) to be used for changing NIS passwords from machines that aren't configured as NIS clients. (This is mostly to allow passwd(1) to work on NIS master servers that aren't configured as clients -- an NIS server need not necessarily be configured as a client itself.) NOTE: Realize that having the ability to specify a domain and hostname lets you use passwd(1) (and chpass(1) too) to submit update requests to yppasswd daemons running on remote servers in remote domains which you may not even be bound to. For example, my machine at home is not an NIS client of the servers on the network that I manage, yet I can easily change my password at work using my FreeBSD box at home by doing: 'passwd -d work.net.domain -h any.nis.server.on.my.net wpaul'. (Yes, I do use securenets at work; temporarily modified my securenets file to give my home system access.) Some people may not be too thrilled with this idea. Those who don't like this feature can recompile passwd(1) and chpass(1) with -DPARANOID to restrict the use of these flags to the superuser. (Oh, I should be adding proper securenets support to ypserv(8) and rpc.yppasswdd(8) over the weekend.) - Merge in changes to allow root on the NIS master server to bypass authentication and change any user's NIS password. (The super-user on the NIS master already has privileges to do this, but doing it through passwd(1) is much easier than updating the maps by hand.) Note that passwd(1) communicates with rpc.yppasswdd(8) via a UNIX domain socket instead of via standard RPC/IP in this case. - Update man page. In chpass(1): - Fix pw_yp.c to work properly in environments where NIS client services aren't available. - Use realloc() instead of malloc() in copy_yp_pass() and copy_local_pass(). - Fix silly bug in copy_yp_pass(); some of the members of the passwd structure weren't being filled in correctly. (This went unnoticed for a while since the old yppasswdd didn't allow changes to the fields that were being botched.) - chpass(1) now also allows the superuser on the NIS master server to make unrestricted changes to any user's NIS password information. - Use UNIX domain comm channel to rpc.yppasswdd(8) when run by the superuser on the NIS master. This allows several new things: o superuser can update an entire master.passwd.{byname,byuid} entry o superuser can update records in arbitrary domains using -d flag to select a domain (before you could only change the default domain) o superuser can _add_ records to the NIS master.passwd maps, provided rpc.yppasswdd(8) has been started with the -a flag (to do this, the superuser must force NIS operation by specifying the -y flag to chpass(1) along with -a, i.e. 'chpass -y -a 'foo:::::::::') - Back out the 'chpass -a <new password entry> breaks with NIS' fix from the last revision and fix it properly this time. The previous revision fixed the immediate problem but broke NIS operation in some cases. - In edit.c, be a little more reasonable about deciding when to prevent the shell field from being changed. Submitted by Charles Owens <owensc@enc.edu>, who said: "I made a minor (one-line) modification to chpass, with regards to whether or not it allows the changing of shells. In the 2.0.5 code, field changing follows the settings specified in the "list" structure defined in table.c . For the shell, though, this is ignored. A quick look in edit.c showed me why, but I don't understand why it was written as such. The logic was if shell is standard shell, allow changing I changed it to if shell changing is allowed (per table.c) and it is a standard shell OR if uid=0, then allow changing." Makes sense to me. - Update man page.
1996-02-23 16:08:59 +00:00
#include <rpcsvc/yp.h>
Bug fix: use the use_yp() function in the chpass(1) code to determine correctly whether a user is local or NIS (or both, or neither). If you have a user that exists locally but not in NIS, passwd(1) could get confused and try to submit the password change to NIS. (Fortunately, yppasswdd is smart enough to spot the error and reject the change.) Bug reported by: Charles Owens <owensc@enc.edu>
1995-09-02 04:02:28 +00:00
int __use_yp = 0;
Merge in changes to support the new rpc.yppasswdd(8) and fix a few bugs. In passwd(1): - Gut most of yp_passwd.c and leave only a few things that aren't common to pw_yp.c. - Add support for -d and -h flags to select domains and NIS server hosts to use when updating NIS passwords. This allows passwd(1) to be used for changing NIS passwords from machines that aren't configured as NIS clients. (This is mostly to allow passwd(1) to work on NIS master servers that aren't configured as clients -- an NIS server need not necessarily be configured as a client itself.) NOTE: Realize that having the ability to specify a domain and hostname lets you use passwd(1) (and chpass(1) too) to submit update requests to yppasswd daemons running on remote servers in remote domains which you may not even be bound to. For example, my machine at home is not an NIS client of the servers on the network that I manage, yet I can easily change my password at work using my FreeBSD box at home by doing: 'passwd -d work.net.domain -h any.nis.server.on.my.net wpaul'. (Yes, I do use securenets at work; temporarily modified my securenets file to give my home system access.) Some people may not be too thrilled with this idea. Those who don't like this feature can recompile passwd(1) and chpass(1) with -DPARANOID to restrict the use of these flags to the superuser. (Oh, I should be adding proper securenets support to ypserv(8) and rpc.yppasswdd(8) over the weekend.) - Merge in changes to allow root on the NIS master server to bypass authentication and change any user's NIS password. (The super-user on the NIS master already has privileges to do this, but doing it through passwd(1) is much easier than updating the maps by hand.) Note that passwd(1) communicates with rpc.yppasswdd(8) via a UNIX domain socket instead of via standard RPC/IP in this case. - Update man page. In chpass(1): - Fix pw_yp.c to work properly in environments where NIS client services aren't available. - Use realloc() instead of malloc() in copy_yp_pass() and copy_local_pass(). - Fix silly bug in copy_yp_pass(); some of the members of the passwd structure weren't being filled in correctly. (This went unnoticed for a while since the old yppasswdd didn't allow changes to the fields that were being botched.) - chpass(1) now also allows the superuser on the NIS master server to make unrestricted changes to any user's NIS password information. - Use UNIX domain comm channel to rpc.yppasswdd(8) when run by the superuser on the NIS master. This allows several new things: o superuser can update an entire master.passwd.{byname,byuid} entry o superuser can update records in arbitrary domains using -d flag to select a domain (before you could only change the default domain) o superuser can _add_ records to the NIS master.passwd maps, provided rpc.yppasswdd(8) has been started with the -a flag (to do this, the superuser must force NIS operation by specifying the -y flag to chpass(1) along with -a, i.e. 'chpass -y -a 'foo:::::::::') - Back out the 'chpass -a <new password entry> breaks with NIS' fix from the last revision and fix it properly this time. The previous revision fixed the immediate problem but broke NIS operation in some cases. - In edit.c, be a little more reasonable about deciding when to prevent the shell field from being changed. Submitted by Charles Owens <owensc@enc.edu>, who said: "I made a minor (one-line) modification to chpass, with regards to whether or not it allows the changing of shells. In the 2.0.5 code, field changing follows the settings specified in the "list" structure defined in table.c . For the shell, though, this is ignored. A quick look in edit.c showed me why, but I don't understand why it was written as such. The logic was if shell is standard shell, allow changing I changed it to if shell changing is allowed (per table.c) and it is a standard shell OR if uid=0, then allow changing." Makes sense to me. - Update man page.
1996-02-23 16:08:59 +00:00
int yp_errno = YP_TRUE;
extern int yp_passwd __P(( char * ));
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
#endif
Update for new kpasswd interface.
1995-01-20 22:03:36 +00:00
#ifdef KERBEROS
#include "krb.h"
#endif
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
#include "extern.h"
Cosmetic in usage string and err() messages.
1997-07-31 06:57:47 +00:00
static void usage __P((void));
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
Update for new kpasswd interface.
1995-01-20 22:03:36 +00:00
int use_local_passwd = 0;
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
int
main(argc, argv)
int argc;
char **argv;
{
int ch;
char *uname;
Ifdefed conditionally-unused variables.
1998-03-23 14:14:24 +00:00
#ifdef KERBEROS
Update for new kpasswd interface.
1995-01-20 22:03:36 +00:00
char *iflag = 0, *rflag = 0, *uflag = 0;
Ifdefed conditionally-unused variables.
1998-03-23 14:14:24 +00:00
#endif
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
#ifdef YP
#ifdef KERBEROS
char realm[REALM_SZ];
Merge in changes to support the new rpc.yppasswdd(8) and fix a few bugs. In passwd(1): - Gut most of yp_passwd.c and leave only a few things that aren't common to pw_yp.c. - Add support for -d and -h flags to select domains and NIS server hosts to use when updating NIS passwords. This allows passwd(1) to be used for changing NIS passwords from machines that aren't configured as NIS clients. (This is mostly to allow passwd(1) to work on NIS master servers that aren't configured as clients -- an NIS server need not necessarily be configured as a client itself.) NOTE: Realize that having the ability to specify a domain and hostname lets you use passwd(1) (and chpass(1) too) to submit update requests to yppasswd daemons running on remote servers in remote domains which you may not even be bound to. For example, my machine at home is not an NIS client of the servers on the network that I manage, yet I can easily change my password at work using my FreeBSD box at home by doing: 'passwd -d work.net.domain -h any.nis.server.on.my.net wpaul'. (Yes, I do use securenets at work; temporarily modified my securenets file to give my home system access.) Some people may not be too thrilled with this idea. Those who don't like this feature can recompile passwd(1) and chpass(1) with -DPARANOID to restrict the use of these flags to the superuser. (Oh, I should be adding proper securenets support to ypserv(8) and rpc.yppasswdd(8) over the weekend.) - Merge in changes to allow root on the NIS master server to bypass authentication and change any user's NIS password. (The super-user on the NIS master already has privileges to do this, but doing it through passwd(1) is much easier than updating the maps by hand.) Note that passwd(1) communicates with rpc.yppasswdd(8) via a UNIX domain socket instead of via standard RPC/IP in this case. - Update man page. In chpass(1): - Fix pw_yp.c to work properly in environments where NIS client services aren't available. - Use realloc() instead of malloc() in copy_yp_pass() and copy_local_pass(). - Fix silly bug in copy_yp_pass(); some of the members of the passwd structure weren't being filled in correctly. (This went unnoticed for a while since the old yppasswdd didn't allow changes to the fields that were being botched.) - chpass(1) now also allows the superuser on the NIS master server to make unrestricted changes to any user's NIS password information. - Use UNIX domain comm channel to rpc.yppasswdd(8) when run by the superuser on the NIS master. This allows several new things: o superuser can update an entire master.passwd.{byname,byuid} entry o superuser can update records in arbitrary domains using -d flag to select a domain (before you could only change the default domain) o superuser can _add_ records to the NIS master.passwd maps, provided rpc.yppasswdd(8) has been started with the -a flag (to do this, the superuser must force NIS operation by specifying the -y flag to chpass(1) along with -a, i.e. 'chpass -y -a 'foo:::::::::') - Back out the 'chpass -a <new password entry> breaks with NIS' fix from the last revision and fix it properly this time. The previous revision fixed the immediate problem but broke NIS operation in some cases. - In edit.c, be a little more reasonable about deciding when to prevent the shell field from being changed. Submitted by Charles Owens <owensc@enc.edu>, who said: "I made a minor (one-line) modification to chpass, with regards to whether or not it allows the changing of shells. In the 2.0.5 code, field changing follows the settings specified in the "list" structure defined in table.c . For the shell, though, this is ignored. A quick look in edit.c showed me why, but I don't understand why it was written as such. The logic was if shell is standard shell, allow changing I changed it to if shell changing is allowed (per table.c) and it is a standard shell OR if uid=0, then allow changing." Makes sense to me. - Update man page.
1996-02-23 16:08:59 +00:00
#define OPTIONS "d:h:lysfoi:r:u:"
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
#else
Merge in changes to support the new rpc.yppasswdd(8) and fix a few bugs. In passwd(1): - Gut most of yp_passwd.c and leave only a few things that aren't common to pw_yp.c. - Add support for -d and -h flags to select domains and NIS server hosts to use when updating NIS passwords. This allows passwd(1) to be used for changing NIS passwords from machines that aren't configured as NIS clients. (This is mostly to allow passwd(1) to work on NIS master servers that aren't configured as clients -- an NIS server need not necessarily be configured as a client itself.) NOTE: Realize that having the ability to specify a domain and hostname lets you use passwd(1) (and chpass(1) too) to submit update requests to yppasswd daemons running on remote servers in remote domains which you may not even be bound to. For example, my machine at home is not an NIS client of the servers on the network that I manage, yet I can easily change my password at work using my FreeBSD box at home by doing: 'passwd -d work.net.domain -h any.nis.server.on.my.net wpaul'. (Yes, I do use securenets at work; temporarily modified my securenets file to give my home system access.) Some people may not be too thrilled with this idea. Those who don't like this feature can recompile passwd(1) and chpass(1) with -DPARANOID to restrict the use of these flags to the superuser. (Oh, I should be adding proper securenets support to ypserv(8) and rpc.yppasswdd(8) over the weekend.) - Merge in changes to allow root on the NIS master server to bypass authentication and change any user's NIS password. (The super-user on the NIS master already has privileges to do this, but doing it through passwd(1) is much easier than updating the maps by hand.) Note that passwd(1) communicates with rpc.yppasswdd(8) via a UNIX domain socket instead of via standard RPC/IP in this case. - Update man page. In chpass(1): - Fix pw_yp.c to work properly in environments where NIS client services aren't available. - Use realloc() instead of malloc() in copy_yp_pass() and copy_local_pass(). - Fix silly bug in copy_yp_pass(); some of the members of the passwd structure weren't being filled in correctly. (This went unnoticed for a while since the old yppasswdd didn't allow changes to the fields that were being botched.) - chpass(1) now also allows the superuser on the NIS master server to make unrestricted changes to any user's NIS password information. - Use UNIX domain comm channel to rpc.yppasswdd(8) when run by the superuser on the NIS master. This allows several new things: o superuser can update an entire master.passwd.{byname,byuid} entry o superuser can update records in arbitrary domains using -d flag to select a domain (before you could only change the default domain) o superuser can _add_ records to the NIS master.passwd maps, provided rpc.yppasswdd(8) has been started with the -a flag (to do this, the superuser must force NIS operation by specifying the -y flag to chpass(1) along with -a, i.e. 'chpass -y -a 'foo:::::::::') - Back out the 'chpass -a <new password entry> breaks with NIS' fix from the last revision and fix it properly this time. The previous revision fixed the immediate problem but broke NIS operation in some cases. - In edit.c, be a little more reasonable about deciding when to prevent the shell field from being changed. Submitted by Charles Owens <owensc@enc.edu>, who said: "I made a minor (one-line) modification to chpass, with regards to whether or not it allows the changing of shells. In the 2.0.5 code, field changing follows the settings specified in the "list" structure defined in table.c . For the shell, though, this is ignored. A quick look in edit.c showed me why, but I don't understand why it was written as such. The logic was if shell is standard shell, allow changing I changed it to if shell changing is allowed (per table.c) and it is a standard shell OR if uid=0, then allow changing." Makes sense to me. - Update man page.
1996-02-23 16:08:59 +00:00
#define OPTIONS "d:h:lysfo"
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
#endif
#else
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
#ifdef KERBEROS
Update for new kpasswd interface.
1995-01-20 22:03:36 +00:00
char realm[REALM_SZ];
#define OPTIONS "li:r:u:"
#else
#define OPTIONS "l"
#endif
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
#endif
#ifdef YP
Bug fix: use the use_yp() function in the chpass(1) code to determine correctly whether a user is local or NIS (or both, or neither). If you have a user that exists locally but not in NIS, passwd(1) could get confused and try to submit the password change to NIS. (Fortunately, yppasswdd is smart enough to spot the error and reject the change.) Bug reported by: Charles Owens <owensc@enc.edu>
1995-09-02 04:02:28 +00:00
int res = 0;
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
Merge in changes to support the new rpc.yppasswdd(8) and fix a few bugs. In passwd(1): - Gut most of yp_passwd.c and leave only a few things that aren't common to pw_yp.c. - Add support for -d and -h flags to select domains and NIS server hosts to use when updating NIS passwords. This allows passwd(1) to be used for changing NIS passwords from machines that aren't configured as NIS clients. (This is mostly to allow passwd(1) to work on NIS master servers that aren't configured as clients -- an NIS server need not necessarily be configured as a client itself.) NOTE: Realize that having the ability to specify a domain and hostname lets you use passwd(1) (and chpass(1) too) to submit update requests to yppasswd daemons running on remote servers in remote domains which you may not even be bound to. For example, my machine at home is not an NIS client of the servers on the network that I manage, yet I can easily change my password at work using my FreeBSD box at home by doing: 'passwd -d work.net.domain -h any.nis.server.on.my.net wpaul'. (Yes, I do use securenets at work; temporarily modified my securenets file to give my home system access.) Some people may not be too thrilled with this idea. Those who don't like this feature can recompile passwd(1) and chpass(1) with -DPARANOID to restrict the use of these flags to the superuser. (Oh, I should be adding proper securenets support to ypserv(8) and rpc.yppasswdd(8) over the weekend.) - Merge in changes to allow root on the NIS master server to bypass authentication and change any user's NIS password. (The super-user on the NIS master already has privileges to do this, but doing it through passwd(1) is much easier than updating the maps by hand.) Note that passwd(1) communicates with rpc.yppasswdd(8) via a UNIX domain socket instead of via standard RPC/IP in this case. - Update man page. In chpass(1): - Fix pw_yp.c to work properly in environments where NIS client services aren't available. - Use realloc() instead of malloc() in copy_yp_pass() and copy_local_pass(). - Fix silly bug in copy_yp_pass(); some of the members of the passwd structure weren't being filled in correctly. (This went unnoticed for a while since the old yppasswdd didn't allow changes to the fields that were being botched.) - chpass(1) now also allows the superuser on the NIS master server to make unrestricted changes to any user's NIS password information. - Use UNIX domain comm channel to rpc.yppasswdd(8) when run by the superuser on the NIS master. This allows several new things: o superuser can update an entire master.passwd.{byname,byuid} entry o superuser can update records in arbitrary domains using -d flag to select a domain (before you could only change the default domain) o superuser can _add_ records to the NIS master.passwd maps, provided rpc.yppasswdd(8) has been started with the -a flag (to do this, the superuser must force NIS operation by specifying the -y flag to chpass(1) along with -a, i.e. 'chpass -y -a 'foo:::::::::') - Back out the 'chpass -a <new password entry> breaks with NIS' fix from the last revision and fix it properly this time. The previous revision fixed the immediate problem but broke NIS operation in some cases. - In edit.c, be a little more reasonable about deciding when to prevent the shell field from being changed. Submitted by Charles Owens <owensc@enc.edu>, who said: "I made a minor (one-line) modification to chpass, with regards to whether or not it allows the changing of shells. In the 2.0.5 code, field changing follows the settings specified in the "list" structure defined in table.c . For the shell, though, this is ignored. A quick look in edit.c showed me why, but I don't understand why it was written as such. The logic was if shell is standard shell, allow changing I changed it to if shell changing is allowed (per table.c) and it is a standard shell OR if uid=0, then allow changing." Makes sense to me. - Update man page.
1996-02-23 16:08:59 +00:00
if (strstr(argv[0], "yppasswd")) __use_yp = 1;
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
#endif
compare return value from getopt against -1 rather than EOF, per the final posix standard on the topic.
1997-03-29 04:34:07 +00:00
while ((ch = getopt(argc, argv, OPTIONS)) != -1) {
Update for new kpasswd interface.
1995-01-20 22:03:36 +00:00
switch (ch) {
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
case 'l': /* change local password file */
Update for new kpasswd interface.
1995-01-20 22:03:36 +00:00
use_local_passwd = 1;
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
break;
Update for new kpasswd interface.
1995-01-20 22:03:36 +00:00
#ifdef KERBEROS
case 'i':
iflag = optarg;
break;
case 'r':
rflag = optarg;
break;
case 'u':
uflag = optarg;
break;
#endif /* KERBEROS */
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
#ifdef YP
case 'y': /* Change NIS password */
Bug fix: use the use_yp() function in the chpass(1) code to determine correctly whether a user is local or NIS (or both, or neither). If you have a user that exists locally but not in NIS, passwd(1) could get confused and try to submit the password change to NIS. (Fortunately, yppasswdd is smart enough to spot the error and reject the change.) Bug reported by: Charles Owens <owensc@enc.edu>
1995-09-02 04:02:28 +00:00
__use_yp = 1;
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
break;
Merge in changes to support the new rpc.yppasswdd(8) and fix a few bugs. In passwd(1): - Gut most of yp_passwd.c and leave only a few things that aren't common to pw_yp.c. - Add support for -d and -h flags to select domains and NIS server hosts to use when updating NIS passwords. This allows passwd(1) to be used for changing NIS passwords from machines that aren't configured as NIS clients. (This is mostly to allow passwd(1) to work on NIS master servers that aren't configured as clients -- an NIS server need not necessarily be configured as a client itself.) NOTE: Realize that having the ability to specify a domain and hostname lets you use passwd(1) (and chpass(1) too) to submit update requests to yppasswd daemons running on remote servers in remote domains which you may not even be bound to. For example, my machine at home is not an NIS client of the servers on the network that I manage, yet I can easily change my password at work using my FreeBSD box at home by doing: 'passwd -d work.net.domain -h any.nis.server.on.my.net wpaul'. (Yes, I do use securenets at work; temporarily modified my securenets file to give my home system access.) Some people may not be too thrilled with this idea. Those who don't like this feature can recompile passwd(1) and chpass(1) with -DPARANOID to restrict the use of these flags to the superuser. (Oh, I should be adding proper securenets support to ypserv(8) and rpc.yppasswdd(8) over the weekend.) - Merge in changes to allow root on the NIS master server to bypass authentication and change any user's NIS password. (The super-user on the NIS master already has privileges to do this, but doing it through passwd(1) is much easier than updating the maps by hand.) Note that passwd(1) communicates with rpc.yppasswdd(8) via a UNIX domain socket instead of via standard RPC/IP in this case. - Update man page. In chpass(1): - Fix pw_yp.c to work properly in environments where NIS client services aren't available. - Use realloc() instead of malloc() in copy_yp_pass() and copy_local_pass(). - Fix silly bug in copy_yp_pass(); some of the members of the passwd structure weren't being filled in correctly. (This went unnoticed for a while since the old yppasswdd didn't allow changes to the fields that were being botched.) - chpass(1) now also allows the superuser on the NIS master server to make unrestricted changes to any user's NIS password information. - Use UNIX domain comm channel to rpc.yppasswdd(8) when run by the superuser on the NIS master. This allows several new things: o superuser can update an entire master.passwd.{byname,byuid} entry o superuser can update records in arbitrary domains using -d flag to select a domain (before you could only change the default domain) o superuser can _add_ records to the NIS master.passwd maps, provided rpc.yppasswdd(8) has been started with the -a flag (to do this, the superuser must force NIS operation by specifying the -y flag to chpass(1) along with -a, i.e. 'chpass -y -a 'foo:::::::::') - Back out the 'chpass -a <new password entry> breaks with NIS' fix from the last revision and fix it properly this time. The previous revision fixed the immediate problem but broke NIS operation in some cases. - In edit.c, be a little more reasonable about deciding when to prevent the shell field from being changed. Submitted by Charles Owens <owensc@enc.edu>, who said: "I made a minor (one-line) modification to chpass, with regards to whether or not it allows the changing of shells. In the 2.0.5 code, field changing follows the settings specified in the "list" structure defined in table.c . For the shell, though, this is ignored. A quick look in edit.c showed me why, but I don't understand why it was written as such. The logic was if shell is standard shell, allow changing I changed it to if shell changing is allowed (per table.c) and it is a standard shell OR if uid=0, then allow changing." Makes sense to me. - Update man page.
1996-02-23 16:08:59 +00:00
case 'd': /* Specify NIS domain. */
#ifdef PARANOID
if (!getuid()) {
#endif
yp_domain = optarg;
if (yp_server == NULL)
yp_server = "localhost";
#ifdef PARANOID
} else {
Cosmetic in usage string and err() messages.
1997-07-31 06:57:47 +00:00
warnx("only the super-user may use the -d flag");
Merge in changes to support the new rpc.yppasswdd(8) and fix a few bugs. In passwd(1): - Gut most of yp_passwd.c and leave only a few things that aren't common to pw_yp.c. - Add support for -d and -h flags to select domains and NIS server hosts to use when updating NIS passwords. This allows passwd(1) to be used for changing NIS passwords from machines that aren't configured as NIS clients. (This is mostly to allow passwd(1) to work on NIS master servers that aren't configured as clients -- an NIS server need not necessarily be configured as a client itself.) NOTE: Realize that having the ability to specify a domain and hostname lets you use passwd(1) (and chpass(1) too) to submit update requests to yppasswd daemons running on remote servers in remote domains which you may not even be bound to. For example, my machine at home is not an NIS client of the servers on the network that I manage, yet I can easily change my password at work using my FreeBSD box at home by doing: 'passwd -d work.net.domain -h any.nis.server.on.my.net wpaul'. (Yes, I do use securenets at work; temporarily modified my securenets file to give my home system access.) Some people may not be too thrilled with this idea. Those who don't like this feature can recompile passwd(1) and chpass(1) with -DPARANOID to restrict the use of these flags to the superuser. (Oh, I should be adding proper securenets support to ypserv(8) and rpc.yppasswdd(8) over the weekend.) - Merge in changes to allow root on the NIS master server to bypass authentication and change any user's NIS password. (The super-user on the NIS master already has privileges to do this, but doing it through passwd(1) is much easier than updating the maps by hand.) Note that passwd(1) communicates with rpc.yppasswdd(8) via a UNIX domain socket instead of via standard RPC/IP in this case. - Update man page. In chpass(1): - Fix pw_yp.c to work properly in environments where NIS client services aren't available. - Use realloc() instead of malloc() in copy_yp_pass() and copy_local_pass(). - Fix silly bug in copy_yp_pass(); some of the members of the passwd structure weren't being filled in correctly. (This went unnoticed for a while since the old yppasswdd didn't allow changes to the fields that were being botched.) - chpass(1) now also allows the superuser on the NIS master server to make unrestricted changes to any user's NIS password information. - Use UNIX domain comm channel to rpc.yppasswdd(8) when run by the superuser on the NIS master. This allows several new things: o superuser can update an entire master.passwd.{byname,byuid} entry o superuser can update records in arbitrary domains using -d flag to select a domain (before you could only change the default domain) o superuser can _add_ records to the NIS master.passwd maps, provided rpc.yppasswdd(8) has been started with the -a flag (to do this, the superuser must force NIS operation by specifying the -y flag to chpass(1) along with -a, i.e. 'chpass -y -a 'foo:::::::::') - Back out the 'chpass -a <new password entry> breaks with NIS' fix from the last revision and fix it properly this time. The previous revision fixed the immediate problem but broke NIS operation in some cases. - In edit.c, be a little more reasonable about deciding when to prevent the shell field from being changed. Submitted by Charles Owens <owensc@enc.edu>, who said: "I made a minor (one-line) modification to chpass, with regards to whether or not it allows the changing of shells. In the 2.0.5 code, field changing follows the settings specified in the "list" structure defined in table.c . For the shell, though, this is ignored. A quick look in edit.c showed me why, but I don't understand why it was written as such. The logic was if shell is standard shell, allow changing I changed it to if shell changing is allowed (per table.c) and it is a standard shell OR if uid=0, then allow changing." Makes sense to me. - Update man page.
1996-02-23 16:08:59 +00:00
}
#endif
break;
case 'h': /* Specify NIS server. */
#ifdef PARANOID
if (!getuid()) {
#endif
yp_server = optarg;
#ifdef PARANOID
} else {
Cosmetic in usage string and err() messages.
1997-07-31 06:57:47 +00:00
warnx("only the super-user may use the -h flag");
Merge in changes to support the new rpc.yppasswdd(8) and fix a few bugs. In passwd(1): - Gut most of yp_passwd.c and leave only a few things that aren't common to pw_yp.c. - Add support for -d and -h flags to select domains and NIS server hosts to use when updating NIS passwords. This allows passwd(1) to be used for changing NIS passwords from machines that aren't configured as NIS clients. (This is mostly to allow passwd(1) to work on NIS master servers that aren't configured as clients -- an NIS server need not necessarily be configured as a client itself.) NOTE: Realize that having the ability to specify a domain and hostname lets you use passwd(1) (and chpass(1) too) to submit update requests to yppasswd daemons running on remote servers in remote domains which you may not even be bound to. For example, my machine at home is not an NIS client of the servers on the network that I manage, yet I can easily change my password at work using my FreeBSD box at home by doing: 'passwd -d work.net.domain -h any.nis.server.on.my.net wpaul'. (Yes, I do use securenets at work; temporarily modified my securenets file to give my home system access.) Some people may not be too thrilled with this idea. Those who don't like this feature can recompile passwd(1) and chpass(1) with -DPARANOID to restrict the use of these flags to the superuser. (Oh, I should be adding proper securenets support to ypserv(8) and rpc.yppasswdd(8) over the weekend.) - Merge in changes to allow root on the NIS master server to bypass authentication and change any user's NIS password. (The super-user on the NIS master already has privileges to do this, but doing it through passwd(1) is much easier than updating the maps by hand.) Note that passwd(1) communicates with rpc.yppasswdd(8) via a UNIX domain socket instead of via standard RPC/IP in this case. - Update man page. In chpass(1): - Fix pw_yp.c to work properly in environments where NIS client services aren't available. - Use realloc() instead of malloc() in copy_yp_pass() and copy_local_pass(). - Fix silly bug in copy_yp_pass(); some of the members of the passwd structure weren't being filled in correctly. (This went unnoticed for a while since the old yppasswdd didn't allow changes to the fields that were being botched.) - chpass(1) now also allows the superuser on the NIS master server to make unrestricted changes to any user's NIS password information. - Use UNIX domain comm channel to rpc.yppasswdd(8) when run by the superuser on the NIS master. This allows several new things: o superuser can update an entire master.passwd.{byname,byuid} entry o superuser can update records in arbitrary domains using -d flag to select a domain (before you could only change the default domain) o superuser can _add_ records to the NIS master.passwd maps, provided rpc.yppasswdd(8) has been started with the -a flag (to do this, the superuser must force NIS operation by specifying the -y flag to chpass(1) along with -a, i.e. 'chpass -y -a 'foo:::::::::') - Back out the 'chpass -a <new password entry> breaks with NIS' fix from the last revision and fix it properly this time. The previous revision fixed the immediate problem but broke NIS operation in some cases. - In edit.c, be a little more reasonable about deciding when to prevent the shell field from being changed. Submitted by Charles Owens <owensc@enc.edu>, who said: "I made a minor (one-line) modification to chpass, with regards to whether or not it allows the changing of shells. In the 2.0.5 code, field changing follows the settings specified in the "list" structure defined in table.c . For the shell, though, this is ignored. A quick look in edit.c showed me why, but I don't understand why it was written as such. The logic was if shell is standard shell, allow changing I changed it to if shell changing is allowed (per table.c) and it is a standard shell OR if uid=0, then allow changing." Makes sense to me. - Update man page.
1996-02-23 16:08:59 +00:00
}
#endif
break;
case 'o':
force_old++;
break;
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
#endif
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
default:
case '?':
usage();
}
Update for new kpasswd interface.
1995-01-20 22:03:36 +00:00
}
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
argc -= optind;
argv += optind;
if ((uname = getlogin()) == NULL)
err(1, "getlogin");
switch(argc) {
case 0:
break;
case 1:
uname = argv[0];
break;
default:
usage();
}
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
#ifdef YP
/*
Patch to fix PR #518. In a system with no NIS, passwd will complain that it can't contact an NIS server when asked to change the password of an invalid user. It should say 'unknown user' instead. The fix is to check for the _PW_KEYYPENABLED flag in the password database and only roll over into the yppasswd stuff if the flag is enabled (this means passwd will not behave as yppasswd if there are no +::::::::: entries in /etc/master.passwd). If NIS is enabled but the user says 'passwd -l foouser' where foouser exists in the NIS maps, but not in /etc/master.passwd, we also say 'unknown user.' This is so we don't outsmart ourselves: specifying the -l flag restricts passwd to the local password database even if NIS is enabled. This change should probably be merged into 2.1.
1995-06-16 03:33:10 +00:00
* If NIS is turned on in the password database, use it, else punt.
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
*/
#ifdef KERBEROS
Bug fix: use the use_yp() function in the chpass(1) code to determine correctly whether a user is local or NIS (or both, or neither). If you have a user that exists locally but not in NIS, passwd(1) could get confused and try to submit the password change to NIS. (Fortunately, yppasswdd is smart enough to spot the error and reject the change.) Bug reported by: Charles Owens <owensc@enc.edu>
1995-09-02 04:02:28 +00:00
if (__use_yp || (iflag == NULL && rflag == NULL && uflag == NULL)) {
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
#endif
Merge in changes to support the new rpc.yppasswdd(8) and fix a few bugs. In passwd(1): - Gut most of yp_passwd.c and leave only a few things that aren't common to pw_yp.c. - Add support for -d and -h flags to select domains and NIS server hosts to use when updating NIS passwords. This allows passwd(1) to be used for changing NIS passwords from machines that aren't configured as NIS clients. (This is mostly to allow passwd(1) to work on NIS master servers that aren't configured as clients -- an NIS server need not necessarily be configured as a client itself.) NOTE: Realize that having the ability to specify a domain and hostname lets you use passwd(1) (and chpass(1) too) to submit update requests to yppasswd daemons running on remote servers in remote domains which you may not even be bound to. For example, my machine at home is not an NIS client of the servers on the network that I manage, yet I can easily change my password at work using my FreeBSD box at home by doing: 'passwd -d work.net.domain -h any.nis.server.on.my.net wpaul'. (Yes, I do use securenets at work; temporarily modified my securenets file to give my home system access.) Some people may not be too thrilled with this idea. Those who don't like this feature can recompile passwd(1) and chpass(1) with -DPARANOID to restrict the use of these flags to the superuser. (Oh, I should be adding proper securenets support to ypserv(8) and rpc.yppasswdd(8) over the weekend.) - Merge in changes to allow root on the NIS master server to bypass authentication and change any user's NIS password. (The super-user on the NIS master already has privileges to do this, but doing it through passwd(1) is much easier than updating the maps by hand.) Note that passwd(1) communicates with rpc.yppasswdd(8) via a UNIX domain socket instead of via standard RPC/IP in this case. - Update man page. In chpass(1): - Fix pw_yp.c to work properly in environments where NIS client services aren't available. - Use realloc() instead of malloc() in copy_yp_pass() and copy_local_pass(). - Fix silly bug in copy_yp_pass(); some of the members of the passwd structure weren't being filled in correctly. (This went unnoticed for a while since the old yppasswdd didn't allow changes to the fields that were being botched.) - chpass(1) now also allows the superuser on the NIS master server to make unrestricted changes to any user's NIS password information. - Use UNIX domain comm channel to rpc.yppasswdd(8) when run by the superuser on the NIS master. This allows several new things: o superuser can update an entire master.passwd.{byname,byuid} entry o superuser can update records in arbitrary domains using -d flag to select a domain (before you could only change the default domain) o superuser can _add_ records to the NIS master.passwd maps, provided rpc.yppasswdd(8) has been started with the -a flag (to do this, the superuser must force NIS operation by specifying the -y flag to chpass(1) along with -a, i.e. 'chpass -y -a 'foo:::::::::') - Back out the 'chpass -a <new password entry> breaks with NIS' fix from the last revision and fix it properly this time. The previous revision fixed the immediate problem but broke NIS operation in some cases. - In edit.c, be a little more reasonable about deciding when to prevent the shell field from being changed. Submitted by Charles Owens <owensc@enc.edu>, who said: "I made a minor (one-line) modification to chpass, with regards to whether or not it allows the changing of shells. In the 2.0.5 code, field changing follows the settings specified in the "list" structure defined in table.c . For the shell, though, this is ignored. A quick look in edit.c showed me why, but I don't understand why it was written as such. The logic was if shell is standard shell, allow changing I changed it to if shell changing is allowed (per table.c) and it is a standard shell OR if uid=0, then allow changing." Makes sense to me. - Update man page.
1996-02-23 16:08:59 +00:00
res = use_yp(uname, 0, 0);
Fix a core dump condition I discovered the other day (right after I installed the last SNAP :). Because of the way the 'use NIS or local?' logic is set up here, it was possible to force the use of the NIS password changer even though the specified user didn't exist in NIS (i.e. # passwd foo, where foo is a local-only user). In this case, we fall intp yp_passwd() without the corresponding yp_password structure being filled in, which leads to an NULL pointer dereference. Also fixed the logic like I just did with chpass so that if the user is both in NIS and the local password database, the program makes a more sensible guess as to which one to use (if NIS is turned on in /etc/master.passwd, then use NIS, else default to local).
1996-10-23 14:50:30 +00:00
if (res == USER_YP_ONLY) {
Patch to fix PR #518. In a system with no NIS, passwd will complain that it can't contact an NIS server when asked to change the password of an invalid user. It should say 'unknown user' instead. The fix is to check for the _PW_KEYYPENABLED flag in the password database and only roll over into the yppasswd stuff if the flag is enabled (this means passwd will not behave as yppasswd if there are no +::::::::: entries in /etc/master.passwd). If NIS is enabled but the user says 'passwd -l foouser' where foouser exists in the NIS maps, but not in /etc/master.passwd, we also say 'unknown user.' This is so we don't outsmart ourselves: specifying the -l flag restricts passwd to the local password database even if NIS is enabled. This change should probably be merged into 2.1.
1995-06-16 03:33:10 +00:00
if (!use_local_passwd) {
exit(yp_passwd(uname));
} else {
/*
* Reject -l flag if NIS is turned on and the user
* doesn't exist in the local password database.
*/
Cosmetic in usage string and err() messages.
1997-07-31 06:57:47 +00:00
errx(1, "unknown local user: %s", uname);
Patch to fix PR #518. In a system with no NIS, passwd will complain that it can't contact an NIS server when asked to change the password of an invalid user. It should say 'unknown user' instead. The fix is to check for the _PW_KEYYPENABLED flag in the password database and only roll over into the yppasswd stuff if the flag is enabled (this means passwd will not behave as yppasswd if there are no +::::::::: entries in /etc/master.passwd). If NIS is enabled but the user says 'passwd -l foouser' where foouser exists in the NIS maps, but not in /etc/master.passwd, we also say 'unknown user.' This is so we don't outsmart ourselves: specifying the -l flag restricts passwd to the local password database even if NIS is enabled. This change should probably be merged into 2.1.
1995-06-16 03:33:10 +00:00
}
Bug fix: use the use_yp() function in the chpass(1) code to determine correctly whether a user is local or NIS (or both, or neither). If you have a user that exists locally but not in NIS, passwd(1) could get confused and try to submit the password change to NIS. (Fortunately, yppasswdd is smart enough to spot the error and reject the change.) Bug reported by: Charles Owens <owensc@enc.edu>
1995-09-02 04:02:28 +00:00
} else if (res == USER_LOCAL_ONLY) {
/*
* Reject -y flag if user only exists locally.
*/
if (__use_yp)
Cosmetic in usage string and err() messages.
1997-07-31 06:57:47 +00:00
errx(1, "unknown NIS user: %s", uname);
Bug fix: use the use_yp() function in the chpass(1) code to determine correctly whether a user is local or NIS (or both, or neither). If you have a user that exists locally but not in NIS, passwd(1) could get confused and try to submit the password change to NIS. (Fortunately, yppasswdd is smart enough to spot the error and reject the change.) Bug reported by: Charles Owens <owensc@enc.edu>
1995-09-02 04:02:28 +00:00
} else if (res == USER_YP_AND_LOCAL) {
Fix a core dump condition I discovered the other day (right after I installed the last SNAP :). Because of the way the 'use NIS or local?' logic is set up here, it was possible to force the use of the NIS password changer even though the specified user didn't exist in NIS (i.e. # passwd foo, where foo is a local-only user). In this case, we fall intp yp_passwd() without the corresponding yp_password structure being filled in, which leads to an NULL pointer dereference. Also fixed the logic like I just did with chpass so that if the user is both in NIS and the local password database, the program makes a more sensible guess as to which one to use (if NIS is turned on in /etc/master.passwd, then use NIS, else default to local).
1996-10-23 14:50:30 +00:00
if (!use_local_passwd && (yp_in_pw_file || __use_yp))
Bug fix: use the use_yp() function in the chpass(1) code to determine correctly whether a user is local or NIS (or both, or neither). If you have a user that exists locally but not in NIS, passwd(1) could get confused and try to submit the password change to NIS. (Fortunately, yppasswdd is smart enough to spot the error and reject the change.) Bug reported by: Charles Owens <owensc@enc.edu>
1995-09-02 04:02:28 +00:00
exit(yp_passwd(uname));
Patch to fix PR #518. In a system with no NIS, passwd will complain that it can't contact an NIS server when asked to change the password of an invalid user. It should say 'unknown user' instead. The fix is to check for the _PW_KEYYPENABLED flag in the password database and only roll over into the yppasswd stuff if the flag is enabled (this means passwd will not behave as yppasswd if there are no +::::::::: entries in /etc/master.passwd). If NIS is enabled but the user says 'passwd -l foouser' where foouser exists in the NIS maps, but not in /etc/master.passwd, we also say 'unknown user.' This is so we don't outsmart ourselves: specifying the -l flag restricts passwd to the local password database even if NIS is enabled. This change should probably be merged into 2.1.
1995-06-16 03:33:10 +00:00
}
#ifdef KERBEROS
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
}
Patch to fix PR #518. In a system with no NIS, passwd will complain that it can't contact an NIS server when asked to change the password of an invalid user. It should say 'unknown user' instead. The fix is to check for the _PW_KEYYPENABLED flag in the password database and only roll over into the yppasswd stuff if the flag is enabled (this means passwd will not behave as yppasswd if there are no +::::::::: entries in /etc/master.passwd). If NIS is enabled but the user says 'passwd -l foouser' where foouser exists in the NIS maps, but not in /etc/master.passwd, we also say 'unknown user.' This is so we don't outsmart ourselves: specifying the -l flag restricts passwd to the local password database even if NIS is enabled. This change should probably be merged into 2.1.
1995-06-16 03:33:10 +00:00
#endif
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
#endif
Update for new kpasswd interface.
1995-01-20 22:03:36 +00:00
if (!use_local_passwd) {
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
#ifdef KERBEROS
Update for new kpasswd interface.
1995-01-20 22:03:36 +00:00
if(krb_get_lrealm(realm, 0) == KSUCCESS) {
fprintf(stderr, "realm %s\n", realm);
exit(krb_passwd(argv[0], iflag, rflag, uflag));
}
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
#endif
Update for new kpasswd interface.
1995-01-20 22:03:36 +00:00
}
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
exit(local_passwd(uname));
}
Cosmetic in usage string and err() messages.
1997-07-31 06:57:47 +00:00
static void
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
usage()
{
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
#ifdef YP
#ifdef KERBEROS
Cosmetic in usage string and err() messages.
1997-07-31 06:57:47 +00:00
fprintf(stderr, "%s\n%s\n",
"usage: passwd [-l] [-i instance] [-r realm] [-u fullname]",
" passwd [-l] [-y] [-o] [-d domain [-h host]] [user]");
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
#else
Cosmetic in usage string and err() messages.
1997-07-31 06:57:47 +00:00
(void)fprintf(stderr,
"usage: passwd [-l] [-y] [-o] [-d domain [-h host]] [user]\n");
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
#endif
#else
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
#ifdef KERBEROS
Update for new kpasswd interface.
1995-01-20 22:03:36 +00:00
fprintf(stderr,
Cosmetic in usage string and err() messages.
1997-07-31 06:57:47 +00:00
"usage: passwd [-l] [-i instance] [-r realm] [-u fullname] [user]\n");
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
#else
(void)fprintf(stderr, "usage: passwd user\n");
Obtained from: The NYS project This is the first round of changes to incorporate YP server functionality into FreeBSD. This particular change allows passwd to change either the local or NIS password, as well as the NIS GECOS and shell information. Essentially, I've taken passwd(1) and yppasswd from the yppasswd-0.5 distribution (which is part of the NYS project -- a project to provide a GNU GPL'ed suite of NIS tools) and rammed them into each other at high speed. I've tried my best to make this co-exist with the Kerberos stuff, but since I don't run Kerberos I don't have an easy way to verify that it all works. If you choose any Kerberos flags then the YP checks should be bypassed, but that may not be enough. I'll modify it some more if it turns out I broke something. For now, support for localand NIS passwords is pretty solid: - If you simply type 'passwd,' the program checks to see if you exist in the local pwd.db database. If not, you get bounced to YP. - If you try to force local functionality with the -l flag and you don't exist locally, you get an error. The -y flag can be used to force YP functionality. -f and -s let you change your full name and shell (respectively). -f *and* -s let you change all of your 'account information.' ypchfn, ypchsh, yppasswd and ypchpass are all links to passwd.
1995-01-31 08:34:16 +00:00
#endif
BSD 4.4 Lite Usr.bin Sources
1994-05-27 12:33:43 +00:00
#endif
exit(1);
}
Reference in New Issue Copy Permalink