Import new rpc.yppasswdd. (Note: accompanying changes to passwd(1) and
chpass(1) are on the way too.) This version supports all the features
of the old one and adds several new ones:
- Supports real multi-domain operation (optional, can be turned
on with a command-line flag). This means you can actually have
several different domains all served from one NIS server and
allow users in any of the supported domains to change their passwords.
The old yppasswdd only allowed changing passwords in the domain
that was set as the system default domain name on the NIS master
server. The new one can change passwords in any domain by trying
to match the user information passed to it against all the passwd
maps it can find. This is something of a hack, but the yppasswd.x
protocol definiton does not allow for a domain to be passwd as an
argument to rpc.yppasswdd, so the server has no choice but to
grope around for a likely match. Since this method can fail if
the same user exists in two domains, this feature is off by default.
If the feature is turned on and the server becomes confused by
duplicate entries, it will abort the update.
- Does not require NIS client services to be available. NIS servers do
_NOT_ necessarily have to be configured as NIS clients in order to
function: the ypserv, ypxfr and yppush programs I've written recently
will operate fine even if the system domain name isn't set, ypbind isn't
running and there are no magic '+' entries in any of the /etc files.
Now rpc.yppasswdd is the same way. The old yppasswdd would not work
like this because it depended on getpwent(3) and friends to look up
users: this will obviously only work if the system where yppasswdd is
running is configured as an NIS client. The new rpc.yppasswdd doesn't
use getpwent(3) at all: instead it searches through the master.passwd
map databases directly. This also makes it easier for it to handle
multiple domains.
- Allows the superuser on the NIS master server to change any user's
password without requiring password authentication. rpc.yppasswdd
creates a UNIX domain socket (/var/run/ypsock) which it monitors
using the same svc_run() loop used to handle incoming RPC requests.
It also clears all the permission bits for /var/run/ypsock; since
this socket is owned by root, this prevents anyone except root from
successfully connect()ing to it. (Using a UNIX domain socket also
prevents IP spoofing attacks.) By building code into passwd(1) and
chpass(1) to take advantage of this 'trusted' channel, the superuser
can use them to send private requests to rpc.yppasswdd.
- Allows the superuser on the NIS master to use chpass(1) to update _all_
of a user's master.passwd information. The UNIX domain access point
accepts a full master.passwd style structure (along with a domain
name and other information), which allows the superuser to update all
of a user's master.passwd information in the NIS master.passwd maps.
Normal users on NIS clients are still only allowed to change their full
name and shell information with chpass.
- Allows the superuser on the NIS master to _add_ records to the NIS
master.passwd maps using chpass(1). This feature is also switchable
with a command-line flag and is off by default.
1996-02-12 15:09:01 +00:00
|
|
|
.\" Copyright (c) 1995, 1996
|
|
|
|
|
.\" Bill Paul <wpaul@ctr.columbia.edu>. 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 Bill Paul.
|
|
|
|
|
.\" 4. Neither the name of the author nor the names of contributors
|
|
|
|
|
.\" may be used to endorse or promote products derived from this software
|
|
|
|
|
.\" without specific prior written permission.
|
|
|
|
|
.\"
|
|
|
|
|
.\" THIS SOFTWARE IS PROVIDED BY Bill Paul 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 Bill Paul 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.
|
|
|
|
|
.\"
|
1997-02-22 16:15:28 +00:00
|
|
|
.\" $Id$
|
Import new rpc.yppasswdd. (Note: accompanying changes to passwd(1) and
chpass(1) are on the way too.) This version supports all the features
of the old one and adds several new ones:
- Supports real multi-domain operation (optional, can be turned
on with a command-line flag). This means you can actually have
several different domains all served from one NIS server and
allow users in any of the supported domains to change their passwords.
The old yppasswdd only allowed changing passwords in the domain
that was set as the system default domain name on the NIS master
server. The new one can change passwords in any domain by trying
to match the user information passed to it against all the passwd
maps it can find. This is something of a hack, but the yppasswd.x
protocol definiton does not allow for a domain to be passwd as an
argument to rpc.yppasswdd, so the server has no choice but to
grope around for a likely match. Since this method can fail if
the same user exists in two domains, this feature is off by default.
If the feature is turned on and the server becomes confused by
duplicate entries, it will abort the update.
- Does not require NIS client services to be available. NIS servers do
_NOT_ necessarily have to be configured as NIS clients in order to
function: the ypserv, ypxfr and yppush programs I've written recently
will operate fine even if the system domain name isn't set, ypbind isn't
running and there are no magic '+' entries in any of the /etc files.
Now rpc.yppasswdd is the same way. The old yppasswdd would not work
like this because it depended on getpwent(3) and friends to look up
users: this will obviously only work if the system where yppasswdd is
running is configured as an NIS client. The new rpc.yppasswdd doesn't
use getpwent(3) at all: instead it searches through the master.passwd
map databases directly. This also makes it easier for it to handle
multiple domains.
- Allows the superuser on the NIS master server to change any user's
password without requiring password authentication. rpc.yppasswdd
creates a UNIX domain socket (/var/run/ypsock) which it monitors
using the same svc_run() loop used to handle incoming RPC requests.
It also clears all the permission bits for /var/run/ypsock; since
this socket is owned by root, this prevents anyone except root from
successfully connect()ing to it. (Using a UNIX domain socket also
prevents IP spoofing attacks.) By building code into passwd(1) and
chpass(1) to take advantage of this 'trusted' channel, the superuser
can use them to send private requests to rpc.yppasswdd.
- Allows the superuser on the NIS master to use chpass(1) to update _all_
of a user's master.passwd information. The UNIX domain access point
accepts a full master.passwd style structure (along with a domain
name and other information), which allows the superuser to update all
of a user's master.passwd information in the NIS master.passwd maps.
Normal users on NIS clients are still only allowed to change their full
name and shell information with chpass.
- Allows the superuser on the NIS master to _add_ records to the NIS
master.passwd maps using chpass(1). This feature is also switchable
with a command-line flag and is off by default.
1996-02-12 15:09:01 +00:00
|
|
|
.\"
|
|
|
|
|
.Dd February 8, 1996
|
|
|
|
|
.Dt RPC.YPPASSWDD 8
|
|
|
|
|
.Os
|
|
|
|
|
.Sh NAME
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
.Nd "server for updating NIS passwords"
|
|
|
|
|
.Sh SYNOPSIS
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
.Op Fl t Ar master.passwd template file
|
|
|
|
|
.Op Fl d Ar default domain
|
|
|
|
|
.Op Fl p Ar path
|
|
|
|
|
.Op Fl s
|
|
|
|
|
.Op Fl f
|
|
|
|
|
.Op Fl a
|
|
|
|
|
.Op Fl m
|
1996-06-05 06:13:09 +00:00
|
|
|
.Op Fl i
|
Import new rpc.yppasswdd. (Note: accompanying changes to passwd(1) and
chpass(1) are on the way too.) This version supports all the features
of the old one and adds several new ones:
- Supports real multi-domain operation (optional, can be turned
on with a command-line flag). This means you can actually have
several different domains all served from one NIS server and
allow users in any of the supported domains to change their passwords.
The old yppasswdd only allowed changing passwords in the domain
that was set as the system default domain name on the NIS master
server. The new one can change passwords in any domain by trying
to match the user information passed to it against all the passwd
maps it can find. This is something of a hack, but the yppasswd.x
protocol definiton does not allow for a domain to be passwd as an
argument to rpc.yppasswdd, so the server has no choice but to
grope around for a likely match. Since this method can fail if
the same user exists in two domains, this feature is off by default.
If the feature is turned on and the server becomes confused by
duplicate entries, it will abort the update.
- Does not require NIS client services to be available. NIS servers do
_NOT_ necessarily have to be configured as NIS clients in order to
function: the ypserv, ypxfr and yppush programs I've written recently
will operate fine even if the system domain name isn't set, ypbind isn't
running and there are no magic '+' entries in any of the /etc files.
Now rpc.yppasswdd is the same way. The old yppasswdd would not work
like this because it depended on getpwent(3) and friends to look up
users: this will obviously only work if the system where yppasswdd is
running is configured as an NIS client. The new rpc.yppasswdd doesn't
use getpwent(3) at all: instead it searches through the master.passwd
map databases directly. This also makes it easier for it to handle
multiple domains.
- Allows the superuser on the NIS master server to change any user's
password without requiring password authentication. rpc.yppasswdd
creates a UNIX domain socket (/var/run/ypsock) which it monitors
using the same svc_run() loop used to handle incoming RPC requests.
It also clears all the permission bits for /var/run/ypsock; since
this socket is owned by root, this prevents anyone except root from
successfully connect()ing to it. (Using a UNIX domain socket also
prevents IP spoofing attacks.) By building code into passwd(1) and
chpass(1) to take advantage of this 'trusted' channel, the superuser
can use them to send private requests to rpc.yppasswdd.
- Allows the superuser on the NIS master to use chpass(1) to update _all_
of a user's master.passwd information. The UNIX domain access point
accepts a full master.passwd style structure (along with a domain
name and other information), which allows the superuser to update all
of a user's master.passwd information in the NIS master.passwd maps.
Normal users on NIS clients are still only allowed to change their full
name and shell information with chpass.
- Allows the superuser on the NIS master to _add_ records to the NIS
master.passwd maps using chpass(1). This feature is also switchable
with a command-line flag and is off by default.
1996-02-12 15:09:01 +00:00
|
|
|
.Op Fl v
|
1996-02-24 22:10:42 +00:00
|
|
|
.Op Fl u
|
Import new rpc.yppasswdd. (Note: accompanying changes to passwd(1) and
chpass(1) are on the way too.) This version supports all the features
of the old one and adds several new ones:
- Supports real multi-domain operation (optional, can be turned
on with a command-line flag). This means you can actually have
several different domains all served from one NIS server and
allow users in any of the supported domains to change their passwords.
The old yppasswdd only allowed changing passwords in the domain
that was set as the system default domain name on the NIS master
server. The new one can change passwords in any domain by trying
to match the user information passed to it against all the passwd
maps it can find. This is something of a hack, but the yppasswd.x
protocol definiton does not allow for a domain to be passwd as an
argument to rpc.yppasswdd, so the server has no choice but to
grope around for a likely match. Since this method can fail if
the same user exists in two domains, this feature is off by default.
If the feature is turned on and the server becomes confused by
duplicate entries, it will abort the update.
- Does not require NIS client services to be available. NIS servers do
_NOT_ necessarily have to be configured as NIS clients in order to
function: the ypserv, ypxfr and yppush programs I've written recently
will operate fine even if the system domain name isn't set, ypbind isn't
running and there are no magic '+' entries in any of the /etc files.
Now rpc.yppasswdd is the same way. The old yppasswdd would not work
like this because it depended on getpwent(3) and friends to look up
users: this will obviously only work if the system where yppasswdd is
running is configured as an NIS client. The new rpc.yppasswdd doesn't
use getpwent(3) at all: instead it searches through the master.passwd
map databases directly. This also makes it easier for it to handle
multiple domains.
- Allows the superuser on the NIS master server to change any user's
password without requiring password authentication. rpc.yppasswdd
creates a UNIX domain socket (/var/run/ypsock) which it monitors
using the same svc_run() loop used to handle incoming RPC requests.
It also clears all the permission bits for /var/run/ypsock; since
this socket is owned by root, this prevents anyone except root from
successfully connect()ing to it. (Using a UNIX domain socket also
prevents IP spoofing attacks.) By building code into passwd(1) and
chpass(1) to take advantage of this 'trusted' channel, the superuser
can use them to send private requests to rpc.yppasswdd.
- Allows the superuser on the NIS master to use chpass(1) to update _all_
of a user's master.passwd information. The UNIX domain access point
accepts a full master.passwd style structure (along with a domain
name and other information), which allows the superuser to update all
of a user's master.passwd information in the NIS master.passwd maps.
Normal users on NIS clients are still only allowed to change their full
name and shell information with chpass.
- Allows the superuser on the NIS master to _add_ records to the NIS
master.passwd maps using chpass(1). This feature is also switchable
with a command-line flag and is off by default.
1996-02-12 15:09:01 +00:00
|
|
|
.Op Fl h
|
|
|
|
|
.Sh DESCRIPTION
|
|
|
|
|
The
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
daemon allows users to change their NIS passwords and certain
|
|
|
|
|
other information using the
|
|
|
|
|
.Xr yppasswd 1
|
|
|
|
|
and
|
|
|
|
|
.Xr ypchpass 1
|
|
|
|
|
commands.
|
|
|
|
|
.Nm Rpc.yppasswdd
|
|
|
|
|
is an RPC-based server that accepts incoming password change requests,
|
|
|
|
|
authenticates them, places the updated information in the
|
|
|
|
|
.Pa /var/yp/master.passwd
|
|
|
|
|
template file and then updates the NIS
|
|
|
|
|
.Pa master.passwd
|
|
|
|
|
and
|
|
|
|
|
.Pa passwd
|
|
|
|
|
maps.
|
|
|
|
|
.Pp
|
|
|
|
|
The
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
server allows a normal NIS user to change
|
|
|
|
|
his or her NIS password, full name (also
|
|
|
|
|
known as 'GECOS' field) or shell. These updates are typically done using
|
|
|
|
|
the
|
|
|
|
|
.Xr yppasswd 1 ,
|
|
|
|
|
.Xr ypchfn 1 ,
|
|
|
|
|
.Xr ypchsh 1 ,
|
|
|
|
|
or
|
|
|
|
|
.Xr ypchpass 1
|
|
|
|
|
commands. (Some administrators don't want users to be able to change their
|
|
|
|
|
full name information or shells; the server can be invoked with option flags
|
|
|
|
|
that disallow such changes.) When the server receives an update request,
|
1996-02-24 22:10:42 +00:00
|
|
|
it compares the address of the client making the request against the
|
|
|
|
|
.Pa securenets
|
|
|
|
|
rules outlined in
|
|
|
|
|
.Pa /var/yp/securenets .
|
|
|
|
|
(See the
|
|
|
|
|
.Xr ypserv 8
|
|
|
|
|
manual page for more information on securenets; the
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
server uses the same access control mechanism as
|
|
|
|
|
.Xr ypserv 8 .)
|
|
|
|
|
.Pp
|
|
|
|
|
The server then
|
|
|
|
|
checks the 'old' password supplied by the user to make sure it's
|
Import new rpc.yppasswdd. (Note: accompanying changes to passwd(1) and
chpass(1) are on the way too.) This version supports all the features
of the old one and adds several new ones:
- Supports real multi-domain operation (optional, can be turned
on with a command-line flag). This means you can actually have
several different domains all served from one NIS server and
allow users in any of the supported domains to change their passwords.
The old yppasswdd only allowed changing passwords in the domain
that was set as the system default domain name on the NIS master
server. The new one can change passwords in any domain by trying
to match the user information passed to it against all the passwd
maps it can find. This is something of a hack, but the yppasswd.x
protocol definiton does not allow for a domain to be passwd as an
argument to rpc.yppasswdd, so the server has no choice but to
grope around for a likely match. Since this method can fail if
the same user exists in two domains, this feature is off by default.
If the feature is turned on and the server becomes confused by
duplicate entries, it will abort the update.
- Does not require NIS client services to be available. NIS servers do
_NOT_ necessarily have to be configured as NIS clients in order to
function: the ypserv, ypxfr and yppush programs I've written recently
will operate fine even if the system domain name isn't set, ypbind isn't
running and there are no magic '+' entries in any of the /etc files.
Now rpc.yppasswdd is the same way. The old yppasswdd would not work
like this because it depended on getpwent(3) and friends to look up
users: this will obviously only work if the system where yppasswdd is
running is configured as an NIS client. The new rpc.yppasswdd doesn't
use getpwent(3) at all: instead it searches through the master.passwd
map databases directly. This also makes it easier for it to handle
multiple domains.
- Allows the superuser on the NIS master server to change any user's
password without requiring password authentication. rpc.yppasswdd
creates a UNIX domain socket (/var/run/ypsock) which it monitors
using the same svc_run() loop used to handle incoming RPC requests.
It also clears all the permission bits for /var/run/ypsock; since
this socket is owned by root, this prevents anyone except root from
successfully connect()ing to it. (Using a UNIX domain socket also
prevents IP spoofing attacks.) By building code into passwd(1) and
chpass(1) to take advantage of this 'trusted' channel, the superuser
can use them to send private requests to rpc.yppasswdd.
- Allows the superuser on the NIS master to use chpass(1) to update _all_
of a user's master.passwd information. The UNIX domain access point
accepts a full master.passwd style structure (along with a domain
name and other information), which allows the superuser to update all
of a user's master.passwd information in the NIS master.passwd maps.
Normal users on NIS clients are still only allowed to change their full
name and shell information with chpass.
- Allows the superuser on the NIS master to _add_ records to the NIS
master.passwd maps using chpass(1). This feature is also switchable
with a command-line flag and is off by default.
1996-02-12 15:09:01 +00:00
|
|
|
valid, then performs some sanity checks on the updated information (these
|
|
|
|
|
include checking for embedded control characters, colons or invalid shells).
|
|
|
|
|
Once it is satisfied that the update request is valid, the server modifies
|
|
|
|
|
the template password file (the default is
|
|
|
|
|
.Pa /var/yp/master.passwd )
|
|
|
|
|
and then runs the
|
|
|
|
|
.Pa /usr/libexec/yppwupdate
|
|
|
|
|
script to rebuild the NIS maps. (This script has two arguments passed
|
|
|
|
|
to it: the absolute pathname of the password template that was modified
|
|
|
|
|
and the name of the domain that is to be updated. These in turn are
|
|
|
|
|
passed to
|
1996-04-08 04:18:31 +00:00
|
|
|
.Pa /var/yp/Makefile ) .
|
Import new rpc.yppasswdd. (Note: accompanying changes to passwd(1) and
chpass(1) are on the way too.) This version supports all the features
of the old one and adds several new ones:
- Supports real multi-domain operation (optional, can be turned
on with a command-line flag). This means you can actually have
several different domains all served from one NIS server and
allow users in any of the supported domains to change their passwords.
The old yppasswdd only allowed changing passwords in the domain
that was set as the system default domain name on the NIS master
server. The new one can change passwords in any domain by trying
to match the user information passed to it against all the passwd
maps it can find. This is something of a hack, but the yppasswd.x
protocol definiton does not allow for a domain to be passwd as an
argument to rpc.yppasswdd, so the server has no choice but to
grope around for a likely match. Since this method can fail if
the same user exists in two domains, this feature is off by default.
If the feature is turned on and the server becomes confused by
duplicate entries, it will abort the update.
- Does not require NIS client services to be available. NIS servers do
_NOT_ necessarily have to be configured as NIS clients in order to
function: the ypserv, ypxfr and yppush programs I've written recently
will operate fine even if the system domain name isn't set, ypbind isn't
running and there are no magic '+' entries in any of the /etc files.
Now rpc.yppasswdd is the same way. The old yppasswdd would not work
like this because it depended on getpwent(3) and friends to look up
users: this will obviously only work if the system where yppasswdd is
running is configured as an NIS client. The new rpc.yppasswdd doesn't
use getpwent(3) at all: instead it searches through the master.passwd
map databases directly. This also makes it easier for it to handle
multiple domains.
- Allows the superuser on the NIS master server to change any user's
password without requiring password authentication. rpc.yppasswdd
creates a UNIX domain socket (/var/run/ypsock) which it monitors
using the same svc_run() loop used to handle incoming RPC requests.
It also clears all the permission bits for /var/run/ypsock; since
this socket is owned by root, this prevents anyone except root from
successfully connect()ing to it. (Using a UNIX domain socket also
prevents IP spoofing attacks.) By building code into passwd(1) and
chpass(1) to take advantage of this 'trusted' channel, the superuser
can use them to send private requests to rpc.yppasswdd.
- Allows the superuser on the NIS master to use chpass(1) to update _all_
of a user's master.passwd information. The UNIX domain access point
accepts a full master.passwd style structure (along with a domain
name and other information), which allows the superuser to update all
of a user's master.passwd information in the NIS master.passwd maps.
Normal users on NIS clients are still only allowed to change their full
name and shell information with chpass.
- Allows the superuser on the NIS master to _add_ records to the NIS
master.passwd maps using chpass(1). This feature is also switchable
with a command-line flag and is off by default.
1996-02-12 15:09:01 +00:00
|
|
|
.Pp
|
|
|
|
|
The FreeBSD version of
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
also allows the super-user on the NIS master server to perform more
|
|
|
|
|
sophisticated updates on the NIS passwd maps. The super-user can modify
|
|
|
|
|
any field in any user's master.passwd entry in any domain, and can
|
|
|
|
|
do so without knowing the user's existing NIS password (when the server
|
|
|
|
|
receives a request from the super-user, the password authentication
|
|
|
|
|
check is bypassed). Furthermore, if the server is invoked with the
|
|
|
|
|
.Fl a
|
|
|
|
|
flag, the super-user can even add new entries to the maps using
|
|
|
|
|
.Xr ypchpass 1 .
|
|
|
|
|
Again, this only applies to the super-user on the NIS
|
|
|
|
|
master server: none of these special functions can be peformed over
|
|
|
|
|
the network.
|
|
|
|
|
.Pp
|
|
|
|
|
The
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
daemon can only be run on a machine that is an NIS master server.
|
|
|
|
|
.Sh OPTIONS
|
|
|
|
|
The following options and flags are supported by
|
|
|
|
|
.Nm rpc.yppasswdd :
|
|
|
|
|
.Bl -tag -width flag
|
|
|
|
|
.It Fl t Ar master.passwd template file
|
|
|
|
|
By default,
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
assumes that the template file used to generates the
|
|
|
|
|
.Pa master.passwd
|
|
|
|
|
and
|
|
|
|
|
.Pa passwd
|
|
|
|
|
maps for the default domain is called
|
|
|
|
|
.Pa /var/yp/master.passwd .
|
|
|
|
|
This default can be overridden by specifying an alternate file name
|
|
|
|
|
with the
|
|
|
|
|
.Fl t
|
|
|
|
|
flag.
|
|
|
|
|
.Pp
|
|
|
|
|
Note: if the template file specified with this flag is
|
|
|
|
|
.Pa /etc/master.passwd ,
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
will also automatically invoke
|
|
|
|
|
.Xr pwd_mkdb 8
|
|
|
|
|
to rebuild the local password databases in addition to the NIS
|
|
|
|
|
maps.
|
|
|
|
|
.It Fl d Ar domain
|
|
|
|
|
The
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
server can support multiple domains, however it must
|
|
|
|
|
choose one domain as a default.
|
|
|
|
|
It will try to use the system default domain name as set by the
|
|
|
|
|
.Xr domainname 1
|
|
|
|
|
command for this default. However,
|
|
|
|
|
if the system domain name is not
|
|
|
|
|
set, a default domain must be specified on
|
|
|
|
|
the command line. If the system default domain is set,
|
|
|
|
|
then this option can be used to override it.
|
|
|
|
|
.It Fl p Ar path
|
|
|
|
|
This option can be used to override the default path to
|
|
|
|
|
the location of the NIS
|
|
|
|
|
map databases. The compiled-in default path is
|
|
|
|
|
.Pa /var/yp .
|
|
|
|
|
.It Fl s
|
|
|
|
|
Disallow changing of shell information.
|
|
|
|
|
.It Fl f
|
|
|
|
|
Disallow changing of full name ('GECOS') information.
|
|
|
|
|
.It Fl a
|
|
|
|
|
Allow additions to be made to the NIS passwd databases. The super-user on the
|
|
|
|
|
NIS master server is permitted to use the
|
|
|
|
|
.Xr ypchpass 1
|
|
|
|
|
command to perform unrestricted modifications to any field in a user's
|
|
|
|
|
.Pa master.passwd
|
|
|
|
|
map entry. When
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
is started with this flag, it will also allow the super-user to add new
|
|
|
|
|
records to the NIS passwd maps, just as is possible when using
|
|
|
|
|
.Xr chpass 1
|
|
|
|
|
to modify the local password database.
|
|
|
|
|
.It Fl m
|
|
|
|
|
Turn on multi-domain mode. Even though
|
|
|
|
|
.Xr ypserv 8
|
|
|
|
|
can handle several simultaneous domains, most implementations of
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
can only operate on a single NIS domain, which is generally the same as
|
|
|
|
|
the system default domain of the NIS master server. The FreeBSD
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
attempts to overcome this problem in spite of the inherent limitations
|
|
|
|
|
of the
|
|
|
|
|
.Pa yppasswd
|
|
|
|
|
protocol, which does not allow for a
|
|
|
|
|
.Pa domain
|
|
|
|
|
argument in client requests. In multi-domain mode,
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
will search through all the passwd maps of all the domains it
|
|
|
|
|
can find under
|
|
|
|
|
.Pa /var/yp
|
|
|
|
|
until it finds an entry that matches the user information specified in
|
|
|
|
|
a given update request. (Matches are determined by checking the username,
|
|
|
|
|
UID and GID fields.) The matched entry and corresponding domain are then
|
|
|
|
|
used for the update.
|
|
|
|
|
.Pp
|
|
|
|
|
Note that in order for multi-domain mode to work, there have to be
|
|
|
|
|
seperate template files for each domain. For example, if a server
|
|
|
|
|
supports three domains,
|
|
|
|
|
.Pa foo ,
|
|
|
|
|
.Pa bar ,
|
|
|
|
|
and
|
|
|
|
|
.Pa baz ,
|
|
|
|
|
there should be three seperate master.passwd template files called
|
|
|
|
|
.Pa /var/yp/foo/master.passwd ,
|
|
|
|
|
.Pa /var/yp/bar/master.passwd ,
|
|
|
|
|
and
|
|
|
|
|
.Pa /var/yp/baz/master.passwd .
|
|
|
|
|
If
|
|
|
|
|
.Pa foo
|
|
|
|
|
happens to be the system default domain, then its template file can
|
|
|
|
|
be either
|
|
|
|
|
.Pa /var/yp/foo/master.passwd
|
|
|
|
|
or
|
|
|
|
|
.Pa /var/yp/master.passwd .
|
|
|
|
|
The server will check for the latter file first and then use the former
|
|
|
|
|
if it can't find it.
|
|
|
|
|
.Pp
|
|
|
|
|
Multi-domain mode is off by default since it can fail if there are
|
|
|
|
|
duplicate or near-duplicate user entries in different domains. The server
|
|
|
|
|
will abort an update request if it finds more than one user entry that
|
|
|
|
|
matches its search criteria. Even so, paranoid administrators
|
|
|
|
|
may wish to leave multi-domain mode disabled.
|
1996-06-05 06:13:09 +00:00
|
|
|
.It Fl i
|
|
|
|
|
If
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
is invoked with this flag, it will perform map updates in place. This
|
|
|
|
|
means that instead of just modifying the password template file and
|
|
|
|
|
starting a map update, the server will modify the map databases
|
|
|
|
|
directly. This is useful when the password maps are large: if, for
|
|
|
|
|
example, the password database has tens of thousands of entries, it
|
|
|
|
|
can take several minutes for a map update to complete. Updating the
|
|
|
|
|
maps in place reduces this time to a few seconds.
|
Import new rpc.yppasswdd. (Note: accompanying changes to passwd(1) and
chpass(1) are on the way too.) This version supports all the features
of the old one and adds several new ones:
- Supports real multi-domain operation (optional, can be turned
on with a command-line flag). This means you can actually have
several different domains all served from one NIS server and
allow users in any of the supported domains to change their passwords.
The old yppasswdd only allowed changing passwords in the domain
that was set as the system default domain name on the NIS master
server. The new one can change passwords in any domain by trying
to match the user information passed to it against all the passwd
maps it can find. This is something of a hack, but the yppasswd.x
protocol definiton does not allow for a domain to be passwd as an
argument to rpc.yppasswdd, so the server has no choice but to
grope around for a likely match. Since this method can fail if
the same user exists in two domains, this feature is off by default.
If the feature is turned on and the server becomes confused by
duplicate entries, it will abort the update.
- Does not require NIS client services to be available. NIS servers do
_NOT_ necessarily have to be configured as NIS clients in order to
function: the ypserv, ypxfr and yppush programs I've written recently
will operate fine even if the system domain name isn't set, ypbind isn't
running and there are no magic '+' entries in any of the /etc files.
Now rpc.yppasswdd is the same way. The old yppasswdd would not work
like this because it depended on getpwent(3) and friends to look up
users: this will obviously only work if the system where yppasswdd is
running is configured as an NIS client. The new rpc.yppasswdd doesn't
use getpwent(3) at all: instead it searches through the master.passwd
map databases directly. This also makes it easier for it to handle
multiple domains.
- Allows the superuser on the NIS master server to change any user's
password without requiring password authentication. rpc.yppasswdd
creates a UNIX domain socket (/var/run/ypsock) which it monitors
using the same svc_run() loop used to handle incoming RPC requests.
It also clears all the permission bits for /var/run/ypsock; since
this socket is owned by root, this prevents anyone except root from
successfully connect()ing to it. (Using a UNIX domain socket also
prevents IP spoofing attacks.) By building code into passwd(1) and
chpass(1) to take advantage of this 'trusted' channel, the superuser
can use them to send private requests to rpc.yppasswdd.
- Allows the superuser on the NIS master to use chpass(1) to update _all_
of a user's master.passwd information. The UNIX domain access point
accepts a full master.passwd style structure (along with a domain
name and other information), which allows the superuser to update all
of a user's master.passwd information in the NIS master.passwd maps.
Normal users on NIS clients are still only allowed to change their full
name and shell information with chpass.
- Allows the superuser on the NIS master to _add_ records to the NIS
master.passwd maps using chpass(1). This feature is also switchable
with a command-line flag and is off by default.
1996-02-12 15:09:01 +00:00
|
|
|
.It Fl v
|
|
|
|
|
Turn on verbose logging mode. The server normally only logs messages
|
|
|
|
|
using the
|
|
|
|
|
.Xr syslog 3
|
|
|
|
|
facility when it encounters an error condition, or when processing
|
|
|
|
|
updates for the super-user on the NIS master server. Running the server
|
|
|
|
|
with the
|
|
|
|
|
.Fl v
|
|
|
|
|
flag will cause it to log informational messages for all updates.
|
1996-02-24 22:10:42 +00:00
|
|
|
.It Fl u
|
|
|
|
|
Many commercial
|
|
|
|
|
.Xr yppasswd 1
|
|
|
|
|
clients do not use a reserved port when sending requests to
|
|
|
|
|
.Nm rpc.yppasswdd .
|
|
|
|
|
This is either because the
|
|
|
|
|
.Xr yppasswd 1
|
|
|
|
|
program is not installed set-uid root, or because the RPC
|
|
|
|
|
implementation does not place any emphasis on binding to reserved
|
|
|
|
|
ports when establishing client connections for the super-user.
|
|
|
|
|
By default,
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
expects to receive requests from clients using reserved ports; requests
|
|
|
|
|
received from non-privileged ports are rejected. Unfortunately, this
|
|
|
|
|
behavior prevents any client systems that to not use privileged
|
|
|
|
|
ports from sucessfully submitting password updates. Specifying
|
|
|
|
|
the
|
|
|
|
|
.Fl u
|
|
|
|
|
flag to
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
disables the privileged port check so that it will work with
|
|
|
|
|
.Xr yppasswd 1
|
|
|
|
|
clients that don't use privileged ports. This reduces security to
|
|
|
|
|
a certain small degree, but it might be necessary in cases where it
|
|
|
|
|
is not possible to change the client behavior.
|
Import new rpc.yppasswdd. (Note: accompanying changes to passwd(1) and
chpass(1) are on the way too.) This version supports all the features
of the old one and adds several new ones:
- Supports real multi-domain operation (optional, can be turned
on with a command-line flag). This means you can actually have
several different domains all served from one NIS server and
allow users in any of the supported domains to change their passwords.
The old yppasswdd only allowed changing passwords in the domain
that was set as the system default domain name on the NIS master
server. The new one can change passwords in any domain by trying
to match the user information passed to it against all the passwd
maps it can find. This is something of a hack, but the yppasswd.x
protocol definiton does not allow for a domain to be passwd as an
argument to rpc.yppasswdd, so the server has no choice but to
grope around for a likely match. Since this method can fail if
the same user exists in two domains, this feature is off by default.
If the feature is turned on and the server becomes confused by
duplicate entries, it will abort the update.
- Does not require NIS client services to be available. NIS servers do
_NOT_ necessarily have to be configured as NIS clients in order to
function: the ypserv, ypxfr and yppush programs I've written recently
will operate fine even if the system domain name isn't set, ypbind isn't
running and there are no magic '+' entries in any of the /etc files.
Now rpc.yppasswdd is the same way. The old yppasswdd would not work
like this because it depended on getpwent(3) and friends to look up
users: this will obviously only work if the system where yppasswdd is
running is configured as an NIS client. The new rpc.yppasswdd doesn't
use getpwent(3) at all: instead it searches through the master.passwd
map databases directly. This also makes it easier for it to handle
multiple domains.
- Allows the superuser on the NIS master server to change any user's
password without requiring password authentication. rpc.yppasswdd
creates a UNIX domain socket (/var/run/ypsock) which it monitors
using the same svc_run() loop used to handle incoming RPC requests.
It also clears all the permission bits for /var/run/ypsock; since
this socket is owned by root, this prevents anyone except root from
successfully connect()ing to it. (Using a UNIX domain socket also
prevents IP spoofing attacks.) By building code into passwd(1) and
chpass(1) to take advantage of this 'trusted' channel, the superuser
can use them to send private requests to rpc.yppasswdd.
- Allows the superuser on the NIS master to use chpass(1) to update _all_
of a user's master.passwd information. The UNIX domain access point
accepts a full master.passwd style structure (along with a domain
name and other information), which allows the superuser to update all
of a user's master.passwd information in the NIS master.passwd maps.
Normal users on NIS clients are still only allowed to change their full
name and shell information with chpass.
- Allows the superuser on the NIS master to _add_ records to the NIS
master.passwd maps using chpass(1). This feature is also switchable
with a command-line flag and is off by default.
1996-02-12 15:09:01 +00:00
|
|
|
.It Fl h
|
|
|
|
|
Displays the list of flags and options understood by
|
|
|
|
|
.Nm rpc.yppasswdd .
|
|
|
|
|
.El
|
|
|
|
|
.Sh FILES
|
|
|
|
|
.Bl -tag -width Pa -compact
|
|
|
|
|
.It Pa /usr/libexec/yppwupdate
|
|
|
|
|
The script invoked by
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
to update and push the NIS maps after
|
|
|
|
|
an update.
|
|
|
|
|
.It Pa /var/yp/master.passwd
|
|
|
|
|
The template password file for the default domain.
|
|
|
|
|
.It Pa /var/yp/[domainname]/[maps]
|
|
|
|
|
The NIS maps for a particular NIS domain.
|
|
|
|
|
.It Pa /var/yp/[domainname]/master.passwd
|
|
|
|
|
The template password file(s) for non-default domains
|
|
|
|
|
(used only in multi-domain mode).
|
|
|
|
|
.El
|
|
|
|
|
.Sh SEE ALSO
|
1997-01-20 00:03:00 +00:00
|
|
|
.Xr yp 4 ,
|
Import new rpc.yppasswdd. (Note: accompanying changes to passwd(1) and
chpass(1) are on the way too.) This version supports all the features
of the old one and adds several new ones:
- Supports real multi-domain operation (optional, can be turned
on with a command-line flag). This means you can actually have
several different domains all served from one NIS server and
allow users in any of the supported domains to change their passwords.
The old yppasswdd only allowed changing passwords in the domain
that was set as the system default domain name on the NIS master
server. The new one can change passwords in any domain by trying
to match the user information passed to it against all the passwd
maps it can find. This is something of a hack, but the yppasswd.x
protocol definiton does not allow for a domain to be passwd as an
argument to rpc.yppasswdd, so the server has no choice but to
grope around for a likely match. Since this method can fail if
the same user exists in two domains, this feature is off by default.
If the feature is turned on and the server becomes confused by
duplicate entries, it will abort the update.
- Does not require NIS client services to be available. NIS servers do
_NOT_ necessarily have to be configured as NIS clients in order to
function: the ypserv, ypxfr and yppush programs I've written recently
will operate fine even if the system domain name isn't set, ypbind isn't
running and there are no magic '+' entries in any of the /etc files.
Now rpc.yppasswdd is the same way. The old yppasswdd would not work
like this because it depended on getpwent(3) and friends to look up
users: this will obviously only work if the system where yppasswdd is
running is configured as an NIS client. The new rpc.yppasswdd doesn't
use getpwent(3) at all: instead it searches through the master.passwd
map databases directly. This also makes it easier for it to handle
multiple domains.
- Allows the superuser on the NIS master server to change any user's
password without requiring password authentication. rpc.yppasswdd
creates a UNIX domain socket (/var/run/ypsock) which it monitors
using the same svc_run() loop used to handle incoming RPC requests.
It also clears all the permission bits for /var/run/ypsock; since
this socket is owned by root, this prevents anyone except root from
successfully connect()ing to it. (Using a UNIX domain socket also
prevents IP spoofing attacks.) By building code into passwd(1) and
chpass(1) to take advantage of this 'trusted' channel, the superuser
can use them to send private requests to rpc.yppasswdd.
- Allows the superuser on the NIS master to use chpass(1) to update _all_
of a user's master.passwd information. The UNIX domain access point
accepts a full master.passwd style structure (along with a domain
name and other information), which allows the superuser to update all
of a user's master.passwd information in the NIS master.passwd maps.
Normal users on NIS clients are still only allowed to change their full
name and shell information with chpass.
- Allows the superuser on the NIS master to _add_ records to the NIS
master.passwd maps using chpass(1). This feature is also switchable
with a command-line flag and is off by default.
1996-02-12 15:09:01 +00:00
|
|
|
.Xr yppush 8 ,
|
1997-01-20 00:03:00 +00:00
|
|
|
.Xr ypserv 8 ,
|
|
|
|
|
.Xr ypxfr 8
|
Import new rpc.yppasswdd. (Note: accompanying changes to passwd(1) and
chpass(1) are on the way too.) This version supports all the features
of the old one and adds several new ones:
- Supports real multi-domain operation (optional, can be turned
on with a command-line flag). This means you can actually have
several different domains all served from one NIS server and
allow users in any of the supported domains to change their passwords.
The old yppasswdd only allowed changing passwords in the domain
that was set as the system default domain name on the NIS master
server. The new one can change passwords in any domain by trying
to match the user information passed to it against all the passwd
maps it can find. This is something of a hack, but the yppasswd.x
protocol definiton does not allow for a domain to be passwd as an
argument to rpc.yppasswdd, so the server has no choice but to
grope around for a likely match. Since this method can fail if
the same user exists in two domains, this feature is off by default.
If the feature is turned on and the server becomes confused by
duplicate entries, it will abort the update.
- Does not require NIS client services to be available. NIS servers do
_NOT_ necessarily have to be configured as NIS clients in order to
function: the ypserv, ypxfr and yppush programs I've written recently
will operate fine even if the system domain name isn't set, ypbind isn't
running and there are no magic '+' entries in any of the /etc files.
Now rpc.yppasswdd is the same way. The old yppasswdd would not work
like this because it depended on getpwent(3) and friends to look up
users: this will obviously only work if the system where yppasswdd is
running is configured as an NIS client. The new rpc.yppasswdd doesn't
use getpwent(3) at all: instead it searches through the master.passwd
map databases directly. This also makes it easier for it to handle
multiple domains.
- Allows the superuser on the NIS master server to change any user's
password without requiring password authentication. rpc.yppasswdd
creates a UNIX domain socket (/var/run/ypsock) which it monitors
using the same svc_run() loop used to handle incoming RPC requests.
It also clears all the permission bits for /var/run/ypsock; since
this socket is owned by root, this prevents anyone except root from
successfully connect()ing to it. (Using a UNIX domain socket also
prevents IP spoofing attacks.) By building code into passwd(1) and
chpass(1) to take advantage of this 'trusted' channel, the superuser
can use them to send private requests to rpc.yppasswdd.
- Allows the superuser on the NIS master to use chpass(1) to update _all_
of a user's master.passwd information. The UNIX domain access point
accepts a full master.passwd style structure (along with a domain
name and other information), which allows the superuser to update all
of a user's master.passwd information in the NIS master.passwd maps.
Normal users on NIS clients are still only allowed to change their full
name and shell information with chpass.
- Allows the superuser on the NIS master to _add_ records to the NIS
master.passwd maps using chpass(1). This feature is also switchable
with a command-line flag and is off by default.
1996-02-12 15:09:01 +00:00
|
|
|
.Sh BUGS
|
|
|
|
|
As listed in the yppasswd.x protocol definition, the YPPASSWDPROC_UPDATE
|
|
|
|
|
procedure takes two arguments: a V7-style passwd structure containing
|
|
|
|
|
updated user information and the user's existing unencrypted (cleartext)
|
|
|
|
|
password. Since
|
|
|
|
|
.Nm rpc.yppasswdd
|
|
|
|
|
is supposed to handle update requests from remote NIS client machines,
|
|
|
|
|
this means that
|
|
|
|
|
.Xr yppasswd 1
|
|
|
|
|
and similar client programs will in fact be transmitting users' cleartext
|
|
|
|
|
passwords over the network.
|
|
|
|
|
.Pp
|
|
|
|
|
This is not a problem for password updates since the plaintext password
|
|
|
|
|
sent with the update will no longer be valid once the new encrypted password
|
|
|
|
|
is put into place, but if the user is only updating his or her 'GECOS'
|
|
|
|
|
information or shell, then the cleartext password sent with the update
|
|
|
|
|
will still be valid once the update is completed. If the network is
|
|
|
|
|
insecure, this cleartext password could be intercepted and used to
|
|
|
|
|
gain unauthorized access to the user's account.
|
|
|
|
|
.Sh AUTHOR
|
|
|
|
|
Bill Paul <wpaul@ctr.columbia.edu>
|
