| ypbind.8 (22997) | ypbind.8 (24945) |
|---|---|
| 1.\" Copyright (c) 1991, 1993, 1995 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 15 unchanged lines hidden (view full) --- 24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" | 1.\" Copyright (c) 1991, 1993, 1995 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 15 unchanged lines hidden (view full) --- 24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" |
| 32.\" $Id$ | 32.\" $Id: ypbind.8,v 1.8 1997/02/22 16:14:54 peter Exp $ |
| 33.\" 34.Dd April 9, 1995 35.Dt YPBIND 8 36.Os 37.Sh NAME 38.Nm ypbind 39.Nd "NIS domain binding daemon" 40.Sh SYNOPSIS | 33.\" 34.Dd April 9, 1995 35.Dt YPBIND 8 36.Os 37.Sh NAME 38.Nm ypbind 39.Nd "NIS domain binding daemon" 40.Sh SYNOPSIS |
| 41.Nm ypbind | 41.Nm |
| 42.Op Fl ypset 43.Op Fl ypsetme 44.Op Fl s 45.Op Fl S Ar domainname,server1,server2,... 46.Sh DESCRIPTION | 42.Op Fl ypset 43.Op Fl ypsetme 44.Op Fl s 45.Op Fl S Ar domainname,server1,server2,... 46.Sh DESCRIPTION |
| 47.Nm ypbind | 47.Nm |
| 48is the process that maintains NIS binding information. At startup, 49it searches for an NIS server responsible for serving the system's 50default domain (as set by the 51.Xr domainname 1 52command) using network broadcasts. 53Once it receives a reply, 54it will store the address of the server and other 55information in a special file located in 56.Pa /var/yp/binding . 57The NIS routines in the standard C library can then use this file 58when processing NIS requests. There may be several such files 59since it is possible for an NIS client to be bound to more than 60one domain. 61.Pp 62After a binding has been established, | 48is the process that maintains NIS binding information. At startup, 49it searches for an NIS server responsible for serving the system's 50default domain (as set by the 51.Xr domainname 1 52command) using network broadcasts. 53Once it receives a reply, 54it will store the address of the server and other 55information in a special file located in 56.Pa /var/yp/binding . 57The NIS routines in the standard C library can then use this file 58when processing NIS requests. There may be several such files 59since it is possible for an NIS client to be bound to more than 60one domain. 61.Pp 62After a binding has been established, |
| 63.Nm ypbind | 63.Nm |
| 64will send DOMAIN_NONACK requests to the NIS server at one minute | 64will send DOMAIN_NONACK requests to the NIS server at one minute |
| 65intervals. If it fails to receive a reply to one of these requests 66.Nm ypbind | 65intervals. If it fails to receive a reply to one of these requests, 66.Nm |
| 67assumes that the server is no longer running and resumes its network 68broadcasts until another binding is established. | 67assumes that the server is no longer running and resumes its network 68broadcasts until another binding is established. |
| 69.Nm ypbind 70will also log warning messages using the syslog(3) facility each time 71it detects that a server has stopped responding, as well as when it 72has bound to a new server. | 69.Nm 70will also log warning messages using the 71.Xr syslog 3 72facility each time it detects that a server has stopped responding, 73as well as when it has bound to a new server. |
| 73.Pp 74.Sh OPTIONS 75The following options are supported by | 74.Pp 75.Sh OPTIONS 76The following options are supported by |
| 76.Nm ypbind : | 77.Nm Ns : |
| 77.Bl -tag -width flag 78.It Fl ypset 79It is possible to force | 78.Bl -tag -width flag 79.It Fl ypset 80It is possible to force |
| 80.Nm ypbind | 81.Nm |
| 81to bind to a particular NIS server host for a given domain by using the 82.Xr ypset 8 83command. However, | 82to bind to a particular NIS server host for a given domain by using the 83.Xr ypset 8 84command. However, |
| 84.Nm ypbind | 85.Nm |
| 85refuses YPBINDPROC_SETDOM requests by default since it has no way of 86knowing exactly who is sending them. Using the 87.Fl ypset 88flag causes | 86refuses YPBINDPROC_SETDOM requests by default since it has no way of 87knowing exactly who is sending them. Using the 88.Fl ypset 89flag causes |
| 89.Nm ypbind | 90.Nm |
| 90to accept YPBINDPROC_SETDOM requests from any host. This option should only 91be used for diagnostic purposes and only for limited periods since allowing 92arbitrary users to reset the binding of an NIS client poses a severe 93security risk. 94.It Fl ypsetme 95This is similar to the 96.Fl ypset 97flag, except that it only permits YPBINDPROC_SETDOM requests to be processed 98if they originated from the local host. 99.It Fl s 100The 101.Fl s 102flag causes | 91to accept YPBINDPROC_SETDOM requests from any host. This option should only 92be used for diagnostic purposes and only for limited periods since allowing 93arbitrary users to reset the binding of an NIS client poses a severe 94security risk. 95.It Fl ypsetme 96This is similar to the 97.Fl ypset 98flag, except that it only permits YPBINDPROC_SETDOM requests to be processed 99if they originated from the local host. 100.It Fl s 101The 102.Fl s 103flag causes |
| 103.Nm ypbind | 104.Nm |
| 104to run in secure mode: it will refuse to bind to any NIS server 105that is not running as root (i.e. that is not using privileged 106TCP ports). 107.It Fl S Ar domainname,server1,server2,server3,... 108The 109.Fl S 110flag allows the system administrator to lock ypbind to a particular 111domain and group of NIS servers. Up to ten servers can be specified. --- 5 unchanged lines hidden (view full) --- 117bind to without the need for specifying the 118.Fl ypset 119or 120.Fl ypsetme 121options, which are often considered to be security holes. The specified 122servers must have valid entries in the local 123.Pa /etc/hosts 124file. IP addresses may be specified in place of hostnames. If | 105to run in secure mode: it will refuse to bind to any NIS server 106that is not running as root (i.e. that is not using privileged 107TCP ports). 108.It Fl S Ar domainname,server1,server2,server3,... 109The 110.Fl S 111flag allows the system administrator to lock ypbind to a particular 112domain and group of NIS servers. Up to ten servers can be specified. --- 5 unchanged lines hidden (view full) --- 118bind to without the need for specifying the 119.Fl ypset 120or 121.Fl ypsetme 122options, which are often considered to be security holes. The specified 123servers must have valid entries in the local 124.Pa /etc/hosts 125file. IP addresses may be specified in place of hostnames. If |
| 125.Nm ypbind | 126.Nm |
| 126can't make sense ouf of the arguments, it will ignore 127the 128.Fl S 129flag and continue running normally. 130.Pp 131Note that | 127can't make sense ouf of the arguments, it will ignore 128the 129.Fl S 130flag and continue running normally. 131.Pp 132Note that |
| 132.Nm ypbind | 133.Nm |
| 133will consider the domainname specified with the 134.Fl S 135flag to be the system default domain. 136.Sh NOTES | 134will consider the domainname specified with the 135.Fl S 136flag to be the system default domain. 137.Sh NOTES |
| 137.Nm ypbind 138will not make continuous attempts to keep secondary domains bound. 139If a server for a second dary domain fails to respond to a ping, 140.Nm ypbind | 138The 139.Nm 140program will not make continuous attempts to keep secondary domains bound. 141If a server for a secondary domain fails to respond to a ping, 142.Nm |
| 141will broadcast for a new server only once before giving up. If a | 143will broadcast for a new server only once before giving up. If a |
| 142client program attempts to reference the unbound domain, ypbind will 143try broadcasting again. By contrast, 144.Nm ypbind | 144client program attempts to reference the unbound domain, 145.Nm 146will try broadcasting again. By contrast, 147.Nm |
| 145will automatically maintain a binding for the default domain whether 146client programs reference it ot not. 147.Sh FILES 148.Bl -tag -width Pa -compact 149.It Pa /var/yp/binding/[domainname].[version] 150The files used to hold binding information for each NIS domain. 151.It Pa /etc/sysconfig 152System configuration file where the system default domain and 153ypbind startup options are specified. 154.El 155.Sh SEE ALSO 156.Xr domainname 1 , 157.Xr syslog 3 , 158.Xr yp 4 , 159.Xr ypserv 8 , 160.Xr ypset 8 161.Sh AUTHOR 162Theo de Raadt <deraadt@fsa.ca> | 148will automatically maintain a binding for the default domain whether 149client programs reference it ot not. 150.Sh FILES 151.Bl -tag -width Pa -compact 152.It Pa /var/yp/binding/[domainname].[version] 153The files used to hold binding information for each NIS domain. 154.It Pa /etc/sysconfig 155System configuration file where the system default domain and 156ypbind startup options are specified. 157.El 158.Sh SEE ALSO 159.Xr domainname 1 , 160.Xr syslog 3 , 161.Xr yp 4 , 162.Xr ypserv 8 , 163.Xr ypset 8 164.Sh AUTHOR 165Theo de Raadt <deraadt@fsa.ca> |