1994-05-27 12:33:43 +00:00
|
|
|
.\" Copyright (c) 1988, 1990, 1993
|
|
|
|
|
.\" 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.
|
|
|
|
|
.\"
|
|
|
|
|
.\" @(#)chpass.1 8.2 (Berkeley) 12/30/93
|
1998-08-14 03:47:38 +00:00
|
|
|
.\" $Id: chpass.1,v 1.7.2.4 1998/08/14 03:38:01 thepish Exp $
|
1994-05-27 12:33:43 +00:00
|
|
|
.\"
|
|
|
|
|
.Dd December 30, 1993
|
|
|
|
|
.Dt CHPASS 1
|
|
|
|
|
.Os
|
|
|
|
|
.Sh NAME
|
1995-08-13 16:12:28 +00:00
|
|
|
.Nm chpass, chfn, chsh, ypchpass, ypchfn, ypchsh
|
1994-05-27 12:33:43 +00:00
|
|
|
.Nd add or change user database information
|
|
|
|
|
.Sh SYNOPSIS
|
1997-06-25 06:59:55 +00:00
|
|
|
.Nm chpass
|
1994-05-27 12:33:43 +00:00
|
|
|
.Op Fl a Ar list
|
1995-01-14 23:14:25 +00:00
|
|
|
.Op Fl p Ar encpass
|
1994-05-27 12:33:43 +00:00
|
|
|
.Op Fl s Ar newshell
|
|
|
|
|
.Op user
|
|
|
|
|
.Sh DESCRIPTION
|
1995-01-14 23:14:25 +00:00
|
|
|
The
|
|
|
|
|
.Nm chpass
|
|
|
|
|
program
|
1994-05-27 12:33:43 +00:00
|
|
|
allows editing of the user database information associated
|
|
|
|
|
with
|
|
|
|
|
.Ar user
|
|
|
|
|
or, by default, the current user.
|
|
|
|
|
The information is formatted and supplied to an editor for changes.
|
|
|
|
|
.Pp
|
|
|
|
|
Only the information that the user is allowed to change is displayed.
|
|
|
|
|
.Pp
|
|
|
|
|
The options are as follows:
|
1995-09-02 03:56:21 +00:00
|
|
|
.Bl -tag -width flag
|
1994-05-27 12:33:43 +00:00
|
|
|
.It Fl a
|
|
|
|
|
The super-user is allowed to directly supply a user database
|
|
|
|
|
entry, in the format specified by
|
|
|
|
|
.Xr passwd 5 ,
|
|
|
|
|
as an argument.
|
|
|
|
|
This argument must be a colon (``:'') separated list of all the
|
|
|
|
|
user database fields, although they may be empty.
|
1995-01-14 23:14:25 +00:00
|
|
|
.It Fl p
|
|
|
|
|
The super-user is allowed to directly supply an encrypted password field,
|
|
|
|
|
in the format used by
|
|
|
|
|
.Xr crypt 3 ,
|
|
|
|
|
as an argument.
|
1994-05-27 12:33:43 +00:00
|
|
|
.It Fl s
|
|
|
|
|
The
|
|
|
|
|
.Fl s
|
|
|
|
|
option attempts to change the user's shell to
|
|
|
|
|
.Ar newshell .
|
|
|
|
|
.El
|
|
|
|
|
.Pp
|
|
|
|
|
Possible display items are as follows:
|
|
|
|
|
.Pp
|
1998-08-14 03:47:38 +00:00
|
|
|
.Bl -tag -width "Other Information:" -compact -offset indent
|
1994-05-27 12:33:43 +00:00
|
|
|
.It Login:
|
|
|
|
|
user's login name
|
|
|
|
|
.It Password:
|
|
|
|
|
user's encrypted password
|
|
|
|
|
.It Uid:
|
|
|
|
|
user's login
|
|
|
|
|
.It Gid:
|
|
|
|
|
user's login group
|
|
|
|
|
.It Change:
|
|
|
|
|
password change time
|
|
|
|
|
.It Expire:
|
|
|
|
|
account expiration time
|
|
|
|
|
.It Class:
|
|
|
|
|
user's general classification
|
|
|
|
|
.It Home Directory:
|
|
|
|
|
user's home directory
|
|
|
|
|
.It Shell:
|
|
|
|
|
user's login shell
|
|
|
|
|
.It Full Name:
|
|
|
|
|
user's real name
|
|
|
|
|
.It Location:
|
|
|
|
|
user's normal location
|
|
|
|
|
.It Home Phone:
|
|
|
|
|
user's home phone
|
|
|
|
|
.It Office Phone:
|
|
|
|
|
user's office phone
|
1998-08-14 03:47:38 +00:00
|
|
|
.It Other Information:
|
|
|
|
|
any locally defined parameters for user
|
1994-05-27 12:33:43 +00:00
|
|
|
.El
|
|
|
|
|
.Pp
|
|
|
|
|
The
|
|
|
|
|
.Ar login
|
|
|
|
|
field is the user name used to access the computer account.
|
|
|
|
|
.Pp
|
|
|
|
|
The
|
|
|
|
|
.Ar password
|
|
|
|
|
field contains the encrypted form of the user's password.
|
|
|
|
|
.Pp
|
|
|
|
|
The
|
|
|
|
|
.Ar uid
|
|
|
|
|
field is the number associated with the
|
|
|
|
|
.Ar login
|
|
|
|
|
field.
|
|
|
|
|
Both of these fields should be unique across the system (and often
|
|
|
|
|
across a group of systems) as they control file access.
|
|
|
|
|
.Pp
|
|
|
|
|
While it is possible to have multiple entries with identical login names
|
|
|
|
|
and/or identical user id's, it is usually a mistake to do so. Routines
|
|
|
|
|
that manipulate these files will often return only one of the multiple
|
|
|
|
|
entries, and that one by random selection.
|
|
|
|
|
.Pp
|
|
|
|
|
The
|
|
|
|
|
.Ar group
|
|
|
|
|
field is the group that the user will be placed in at login.
|
|
|
|
|
Since BSD supports multiple groups (see
|
|
|
|
|
.Xr groups 1 )
|
|
|
|
|
this field currently has little special meaning.
|
|
|
|
|
This field may be filled in with either a number or a group name (see
|
|
|
|
|
.Xr group 5 ) .
|
|
|
|
|
.Pp
|
|
|
|
|
The
|
|
|
|
|
.Ar change
|
|
|
|
|
field is the date by which the password must be changed.
|
|
|
|
|
.Pp
|
|
|
|
|
The
|
|
|
|
|
.Ar expire
|
|
|
|
|
field is the date on which the account expires.
|
|
|
|
|
.Pp
|
|
|
|
|
Both the
|
|
|
|
|
.Ar change
|
|
|
|
|
and
|
|
|
|
|
.Ar expire
|
|
|
|
|
fields should be entered in the form ``month day year'' where
|
|
|
|
|
.Ar month
|
|
|
|
|
is the month name (the first three characters are sufficient),
|
|
|
|
|
.Ar day
|
|
|
|
|
is the day of the month, and
|
|
|
|
|
.Ar year
|
|
|
|
|
is the year.
|
|
|
|
|
.Pp
|
|
|
|
|
The
|
|
|
|
|
.Ar class
|
|
|
|
|
field is currently unused. In the near future it will be a key to
|
|
|
|
|
a
|
|
|
|
|
.Xr termcap 5
|
|
|
|
|
style database of user attributes.
|
|
|
|
|
.Pp
|
|
|
|
|
The user's
|
|
|
|
|
.Ar home directory
|
|
|
|
|
is the full UNIX path name where the user
|
|
|
|
|
will be placed at login.
|
|
|
|
|
.Pp
|
|
|
|
|
The
|
|
|
|
|
.Ar shell
|
|
|
|
|
field is the command interpreter the user prefers.
|
|
|
|
|
If the
|
|
|
|
|
.Ar shell
|
|
|
|
|
field is empty, the Bourne shell,
|
|
|
|
|
.Pa /bin/sh ,
|
|
|
|
|
is assumed.
|
|
|
|
|
When altering a login shell, and not the super-user, the user
|
|
|
|
|
may not change from a non-standard shell or to a non-standard
|
|
|
|
|
shell.
|
|
|
|
|
Non-standard is defined as a shell not found in
|
|
|
|
|
.Pa /etc/shells .
|
|
|
|
|
.Pp
|
1998-08-14 03:47:38 +00:00
|
|
|
The last five fields are for storing the user's
|
1994-05-27 12:33:43 +00:00
|
|
|
.Ar full name , office location ,
|
1998-06-13 19:14:14 +00:00
|
|
|
.Ar work
|
1994-05-27 12:33:43 +00:00
|
|
|
and
|
1998-06-13 19:14:14 +00:00
|
|
|
.Ar home telephone
|
1998-08-14 03:47:38 +00:00
|
|
|
numbers and finally
|
|
|
|
|
.Ar other information
|
|
|
|
|
which is a single comma delimited string to represent any additional
|
|
|
|
|
gcos fields (typically used for site specific user information).
|
1994-05-27 12:33:43 +00:00
|
|
|
.Pp
|
|
|
|
|
Once the information has been verified,
|
|
|
|
|
.Nm chpass
|
|
|
|
|
uses
|
|
|
|
|
.Xr pwd_mkdb 8
|
|
|
|
|
to update the user database.
|
|
|
|
|
.Sh ENVIRONMENT
|
|
|
|
|
The
|
|
|
|
|
.Xr vi 1
|
|
|
|
|
editor will be used unless the environment variable EDITOR is set to
|
|
|
|
|
an alternate editor.
|
|
|
|
|
When the editor terminates, the information is re-read and used to
|
|
|
|
|
update the user database itself.
|
|
|
|
|
Only the user, or the super-user, may edit the information associated
|
|
|
|
|
with the user.
|
1995-08-13 16:12:28 +00:00
|
|
|
.Sh NIS INTERACTION
|
|
|
|
|
.Nm Chpass
|
|
|
|
|
can also be used in conjunction with NIS, however some restrictions
|
|
|
|
|
apply.
|
|
|
|
|
Currently,
|
|
|
|
|
.Nm chpass
|
|
|
|
|
can only make changes to the NIS passwd maps through
|
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
|
|
|
.Xr rpc.yppasswdd 8 ,
|
|
|
|
|
which normally only permits changes to a user's password, shell and GECOS
|
|
|
|
|
fields. Except when invoked by the super-user on the NIS master server,
|
|
|
|
|
.Nm chpass
|
|
|
|
|
(and, similarly,
|
|
|
|
|
.Xr passwd 1 )
|
|
|
|
|
can not use the
|
|
|
|
|
.Xr rpc.yppasswdd 8
|
|
|
|
|
server to change other user information or
|
|
|
|
|
add new records to the NIS passwd maps.
|
1995-08-13 16:12:28 +00:00
|
|
|
Furthermore,
|
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
|
|
|
.Xr rpc.yppasswdd 8
|
1995-08-13 16:12:28 +00:00
|
|
|
requires password authentication before it will make any
|
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
|
|
|
changes. The only user allowed to submit changes without supplying
|
|
|
|
|
a password is the super-user on the NIS master server; all other users,
|
|
|
|
|
including those with root privileges on NIS clients (and NIS slave
|
|
|
|
|
servers) must enter a password.
|
|
|
|
|
(The super-user on the NIS master is allowed to bypass these restrictions
|
|
|
|
|
largely for convenience: a user with root access
|
|
|
|
|
to the NIS master server already has the privileges required to make
|
|
|
|
|
updates to the NIS maps, but editing the map source files by hand can
|
|
|
|
|
be cumbersome.
|
|
|
|
|
.Pp
|
|
|
|
|
Note: these exceptions only apply when the NIS master server is a
|
|
|
|
|
FreeBSD system.)
|
1995-08-13 16:12:28 +00:00
|
|
|
.Pp
|
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
|
|
|
Consequently, except where noted, the following restrictions apply when
|
1995-08-13 16:12:28 +00:00
|
|
|
.Nm chpass
|
|
|
|
|
is used with NIS:
|
|
|
|
|
.Bl -enum -offset indent
|
|
|
|
|
.It
|
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
|
|
|
.Pa Only the shell and GECOS information may be changed.
|
1995-08-13 16:12:28 +00:00
|
|
|
All other
|
|
|
|
|
fields are restricted, even when
|
|
|
|
|
.Nm chpass
|
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
|
|
|
is invoked by the super-user.
|
|
|
|
|
While support for
|
1995-08-13 16:12:28 +00:00
|
|
|
changing other fields could be added, this would lead to
|
|
|
|
|
compatibility problems with other NIS-capable systems.
|
|
|
|
|
Even though the super-user may supply data for other fields
|
|
|
|
|
while editing an entry, the extra information (other than the
|
|
|
|
|
password -- see below) will be silently discarded.
|
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
|
|
|
.Pp
|
|
|
|
|
Exception: the super-user on the NIS master server is permitted to
|
|
|
|
|
change any field.
|
|
|
|
|
.Pp
|
1995-08-13 16:12:28 +00:00
|
|
|
.It
|
|
|
|
|
.Pa Password authentication is required.
|
|
|
|
|
.Nm Chpass
|
|
|
|
|
will prompt for the user's NIS password before effecting
|
|
|
|
|
any changes. If the password is invalid, all changes will be
|
|
|
|
|
discarded.
|
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
|
|
|
.Pp
|
|
|
|
|
Exception: the super-user on the NIS master server is allowed to
|
|
|
|
|
submit changes without supplying a password. (The super-user may
|
|
|
|
|
choose to turn off this feature using the
|
|
|
|
|
.Fl o
|
|
|
|
|
flag, described below.)
|
1995-08-13 16:12:28 +00:00
|
|
|
.It
|
|
|
|
|
.Pa Adding new records to the local
|
|
|
|
|
.Pa password database is discouraged.
|
|
|
|
|
.Nm Chpass
|
|
|
|
|
will allow the administrator to add new records to the
|
|
|
|
|
local password database while NIS is enabled, but this can lead to
|
|
|
|
|
some confusion since the new records are appended to the end of
|
|
|
|
|
the master password file, usually after the special NIS '+' entries.
|
|
|
|
|
The administrator should use
|
|
|
|
|
.Xr vipw 8
|
|
|
|
|
to modify the local password
|
|
|
|
|
file when NIS is running.
|
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
|
|
|
.Pp
|
|
|
|
|
The super-user on the NIS master server is permitted to add new records
|
|
|
|
|
to the NIS password maps, provided the
|
|
|
|
|
.Xr rpc.yppasswdd 8
|
|
|
|
|
server has been started with the
|
|
|
|
|
.Fl a
|
|
|
|
|
flag to permitted additions (it refuses them by default).
|
|
|
|
|
.Nm Chpass
|
|
|
|
|
tries to update the local password database by default; to update the
|
|
|
|
|
NIS maps instead, invoke chpass with the
|
|
|
|
|
.Fl y
|
|
|
|
|
flag.
|
1995-08-13 16:12:28 +00:00
|
|
|
.It
|
|
|
|
|
.Pa Password changes are not permitted.
|
|
|
|
|
Users should use
|
|
|
|
|
.Xr passwd 1
|
|
|
|
|
or
|
|
|
|
|
.Xr yppasswd 1
|
|
|
|
|
to change their NIS passwords. The super-user is allowed to specify
|
|
|
|
|
a new password (even though the ``Password:'' field does not show
|
|
|
|
|
up in the editor template, the super-user may add it back by hand),
|
|
|
|
|
but even the super-user must supply the user's original password
|
|
|
|
|
otherwise
|
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
|
|
|
.Xr rpc.yppasswdd 8
|
1995-08-13 16:12:28 +00:00
|
|
|
will refuse to update the NIS maps.
|
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
|
|
|
.Pp
|
|
|
|
|
Exception: the super-user on the NIS master server is permitted to
|
|
|
|
|
change a user's NIS password with
|
|
|
|
|
.Nm chpass .
|
1995-08-13 16:12:28 +00:00
|
|
|
.El
|
1995-09-02 03:56:21 +00:00
|
|
|
.Pp
|
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
|
|
|
There are also a few extra option flags that are available when
|
1995-09-02 03:56:21 +00:00
|
|
|
.Nm chpass
|
1995-09-02 19:25:40 +00:00
|
|
|
is compiled with NIS support:
|
1995-09-02 03:56:21 +00:00
|
|
|
.Bl -tag -width flag
|
|
|
|
|
.It Fl l
|
|
|
|
|
The
|
|
|
|
|
.Fl l
|
|
|
|
|
flag forces
|
|
|
|
|
.Nm chpass
|
|
|
|
|
to modify the local copy of a user's password
|
|
|
|
|
information in the even that a user exists in both
|
|
|
|
|
the local and NIS databases.
|
|
|
|
|
.It Fl y
|
|
|
|
|
This flag has the opposite effect of
|
|
|
|
|
.Fl l .
|
|
|
|
|
This flag is largely redundant since
|
|
|
|
|
.Nm chpass
|
|
|
|
|
operates on NIS entries by default if NIS is enabled.
|
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
|
|
|
.It Fl d Ar domain
|
|
|
|
|
Specify a particular NIS domain.
|
|
|
|
|
.Nm Chpass
|
|
|
|
|
uses the system domain name by default, as set by the
|
|
|
|
|
.Xr domainname 1
|
|
|
|
|
command. The
|
|
|
|
|
.Fl d
|
|
|
|
|
option can be used to override a default, or to specify a domain
|
|
|
|
|
when the system domain name is not set.
|
|
|
|
|
.It Fl h Ar host
|
|
|
|
|
Specify the name or address of an NIS server to query. Normally,
|
|
|
|
|
.Nm chpass
|
|
|
|
|
will communicate with the NIS master host specified in the
|
|
|
|
|
.Pa master.passwd
|
|
|
|
|
or
|
|
|
|
|
.Pa passwd
|
|
|
|
|
maps. On hosts that have not been configured as NIS clients, there is
|
|
|
|
|
no way for the program to determine this information unless the user
|
|
|
|
|
provides the hostname of a server. Note that the specified hostname need
|
|
|
|
|
not be that of the NIS master server; the name of any server, master or
|
|
|
|
|
slave, in a given NIS domain will do.
|
|
|
|
|
.Pp
|
|
|
|
|
When using the
|
|
|
|
|
.Fl d
|
|
|
|
|
option, the hostname defaults to ``localhost.'' The
|
|
|
|
|
.Fl h
|
|
|
|
|
option can be used in conjunction with the
|
|
|
|
|
.Fl d
|
|
|
|
|
option, in which case the user-specified hostname will override
|
|
|
|
|
the default.
|
|
|
|
|
.Pp
|
|
|
|
|
.It Fl o
|
|
|
|
|
Force the use of RPC-based updates when communicating with
|
|
|
|
|
.Xr rpc.yppasswdd 8
|
|
|
|
|
(``old-mode'').
|
|
|
|
|
When invoked by the super-user on the NIS master server,
|
|
|
|
|
.Nm chpass
|
|
|
|
|
allows unrestricted changes to the NIS passwd maps using dedicated,
|
|
|
|
|
non-RPC-based mechanism (in this case, a UNIX domain socket). The
|
|
|
|
|
.Fl o
|
|
|
|
|
flag can be used to force
|
|
|
|
|
.Nm chpass
|
|
|
|
|
to use the standard update mechanism instead. This option is provided
|
|
|
|
|
mainly for testing purposes.
|
1995-09-02 03:56:21 +00:00
|
|
|
.El
|
|
|
|
|
.Pp
|
1994-05-27 12:33:43 +00:00
|
|
|
.Sh FILES
|
|
|
|
|
.Bl -tag -width /etc/master.passwd -compact
|
|
|
|
|
.It Pa /etc/master.passwd
|
|
|
|
|
The user database
|
|
|
|
|
.It Pa /etc/passwd
|
|
|
|
|
A Version 7 format password file
|
|
|
|
|
.It Pa /etc/chpass.XXXXXX
|
|
|
|
|
Temporary copy of the password file
|
|
|
|
|
.It Pa /etc/shells
|
|
|
|
|
The list of approved shells
|
|
|
|
|
.El
|
|
|
|
|
.Sh SEE ALSO
|
|
|
|
|
.Xr finger 1 ,
|
1997-01-15 23:25:55 +00:00
|
|
|
.Xr login 1 ,
|
1994-05-27 12:33:43 +00:00
|
|
|
.Xr passwd 1 ,
|
|
|
|
|
.Xr getusershell 3 ,
|
|
|
|
|
.Xr passwd 5 ,
|
|
|
|
|
.Xr pwd_mkdb 8 ,
|
|
|
|
|
.Xr vipw 8
|
|
|
|
|
.Rs
|
|
|
|
|
.%A Robert Morris
|
|
|
|
|
and
|
|
|
|
|
.%A Ken Thompson
|
|
|
|
|
.%T "UNIX Password security"
|
|
|
|
|
.Re
|
1995-08-13 16:12:28 +00:00
|
|
|
.Sh NOTES
|
|
|
|
|
The
|
|
|
|
|
.Xr chfn 1 ,
|
|
|
|
|
.Xr chsh 1 ,
|
|
|
|
|
.Xr ypchpass 1 ,
|
|
|
|
|
.Xr ypchfn 1
|
|
|
|
|
and
|
1996-02-14 22:26:04 +00:00
|
|
|
.Xr ypchsh 1
|
1995-08-13 16:12:28 +00:00
|
|
|
commands are really only links to
|
|
|
|
|
.Nm chpass .
|
1994-05-27 12:33:43 +00:00
|
|
|
.Sh BUGS
|
|
|
|
|
User information should (and eventually will) be stored elsewhere.
|
|
|
|
|
.Sh HISTORY
|
|
|
|
|
The
|
|
|
|
|
.Nm
|
|
|
|
|
command appeared in
|
|
|
|
|
.Bx 4.3 Reno .
|
