ypserv(8) [opendarwin man page]

YPSERV(8)						    BSD System Manager's Manual 						 YPSERV(8)

NAME

     ypserv -- YP server daemon

SYNOPSIS

     ypserv [-1] [-a aclfile] [-d] [-x]

DESCRIPTION

     Ypserv is a fundamental part of the network information system called YP.	This server provides information from YP maps to the YP clients on
     the network.

     A YP map is stored on the server as a db(3) database. A number of YP maps is grouped together in a domain.  Ypserv determines the domains it
     serves by looking for a directory with the domain name in /var/yp.

     YP hasn't been known for high security through the years. In recent years security has improved by restricting access to the server. In SunOS
     4.1 has a new file occured named /var/yp/securenet.  It contains networks the server can assume is secure. For information about file format
     see securenet(5).

     Before the author of this server had seen securenet(5) another format was implemented ypserv.acl(5).  This file format makes it possible to
     allow and deny hosts and networks access to the server. This file can have any name since it's given by the argument to -a (use full path).

     The file used can be reread by sending a SIGHUP to ypserv. The process pid can be found in the file /var/run/ypserv.pid

     If a host isn't secure all queries to the server will result in a YP_NODOM result.

     If the file /var/yp/ypserv.log exists then messages will be written to the file.

     If a directory named the same as the system domainname exists in /var/yp/ (ie. the domainname is foo and directory /var/yp/foo exists), then
     ypserv will be automatically started at boot time.

     The options are as follows:

     -1      Allow ypserv to answer old YP version 1 requests.

     -a aclfile
	     Don't use /var/yp/securenet.  Use another file with another file format. For futher information see man page for ypserv.acl.

     -d      Use Internet Domain Name System. If a query to map hosts.byname or hosts.byaddr fails, make a DNS query and return the result if suc-
	     cessful.  Alternately, if these maps were built on the YP master using makedbm -b then DNS queries will be done without needing to
	     specify -d.

     -x      Terminate the server after processing aclfile or /var/yp/securenet.

FILES

     /var/yp/ypserv.log
     /var/yp/securenet
     /var/run/ypserv.pid

SEE ALSO

     yp(8), ypserv.acl(5), securenet(5), ypbind(1)

AUTHOR

     Mats O Jansson <moj@stacken.kth.se>

BSD
								   June 27, 1994							       BSD

YPSERV.ACL(5)						      BSD File Formats Manual						     YPSERV.ACL(5)

NAME

     ypserv.acl -- ypserv(8) configuration file

DESCRIPTION

     The ypserv.acl file controls which hosts can connect to the YP server.

     The format is more complex than the format for securenet(5).  The first two verbs on each line controls if the line will allow or deny access
     for a host, network (net) or all hosts.

     The YP server reads the configuration file and build a list in memory. This list is processed from the beginning for every incomming request.
     As soon a match is found in the list the search terminates and it returns success or failure depending on allow or deny.  If no match was
     found in the list success is returned.

     If access is denied every call will cause a no such domain error for the caller.

     Don't forget to allow localhost access if you want the machine running ypserv access it too.

     There is no default name for this file. Start ypserv with a -a filename to read a file with this format.

     The following different syntax can be used:

     < allow|deny > host < hostname|ip-address >

     If hostname has more than one ip address then all will be added to the list.

     < allow|deny > net < netname|netnumber > [netmask <netname|netnumber>]

     If netmask part of the command isn't given then the netmask will be assumed to be a class A, B or C net depending on the net number.

     < allow|deny > all

     A line containing one of these commands will always match any host.

EXAMPLES

     A configuration file might appear as follows:

     # This is an example of an access control file to be used by ypserv.
     #
     # This file is parsed line by line. First match will terminate the check
     # of the caller.
     #

     ###########################################################################
     # This is the commands that will match a single host
     #
     #	     allow host <hostname|ip-address>
     #	     deny host <hostname|ip-address>
     #
     # To process hostname gethostbyname is called. If the hostname has
     # multiple ip-addresses all will be added (I hope). ip-address
     # processed by inet_aton.
     allow host localhost
     deny host jodie

     ###########################################################################
     # This is the commands that will match a network
     #
     #	     allow net <netname|netnumber> [netmask <netname|netnumber>]
     #	     deny net <netname|netnumber> [netmask <netname|netnumber>]
     #
     # To process netname getnetbyname is called, and inet_aton is used for
     # netnumber. inet_aton both access numbers as 255.255.255.0 and 0xffffff00.
     #
     # If netmask isn't given the parser will assume netmask from the first bits
     # of the network number. So if the network is subneted the you have to add
     # the netmask. In my case I've got the network 139.58.253.0 at home so too
     # allow any of my computers to talk with the server I need the following
     # line
     #
     allow net mojathome netmask 255.255.255.0

     ###########################################################################
     # At last we have a command that will match any caller:
     #
     #	     allow all
     #	     deny all
     #

     # reject all connections
     deny all

FILES

     /var/yp/ypserv.acl  A ypserv(8) configuration file.

SEE ALSO

     yp(8), ypserv(8), securenet(5)

AUTHOR

     Mats O Jansson <moj@stacken.kth.se>

BSD
								   July 2, 1994 							       BSD