NetBSD/usr.sbin/portmap/portmap.8

153 lines
4.2 KiB
Groff

.\" $NetBSD: portmap.8,v 1.8 1999/08/02 16:05:40 bouyer Exp $
.\"
.\" Copyright (c) 1987 Sun Microsystems
.\" Copyright (c) 1990, 1991, 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.
.\"
.\" from: @(#)portmap.8 8.1 (Berkeley) 6/6/93
.\"
.Dd June 6, 1993
.Dt PORTMAP 8
.Os
.Sh NAME
.Nm portmap
.Nd
.Tn RPC
program number to
.Tn DARPA
port mapper
.Sh SYNOPSIS
.Nm
.Op Fl dils
.Sh DESCRIPTION
.Nm
is a server that converts
.Tn RPC
program numbers into
.Tn DARPA
protocol port numbers.
It must be running in order to make
.Tn RPC
calls.
.Pp
When an
.Tn RPC
server is started, it will tell
.Nm
what port number it is listening to, and what
.Tn RPC
program numbers it is prepared to serve.
When a client wishes to make an
.Tn RPC
call to a given program number,
it will first contact
.Nm
on the server machine to determine
the port number where
.Tn RPC
packets should be sent.
.Pp
.Nm
must be started before any
.Tn RPC
servers are invoked.
.Pp
Normally
.Nm
forks and dissociates itself from the terminal
like any other daemon.
.Nm
then logs errors using
.Xr syslog 3 .
.Pp
.Nm
uses
.Xr libwrap
style access control (the
.Pa /etc/hosts.allow
and
.Pa /etc/hosts.deny
files)
to control access to the portmapper itself and control forwarding
of requests. This prevents clients from using
.Nm
to circumvent host-based services in individual services.
.Pp
Option available:
.Bl -tag -width Ds
.It Fl d
prevents
.Nm
from running as a daemon,
and causes errors and debugging information
to be printed to the standard error output.
.It Fl i
.Dq insecure
mode. Allows to call PMAPPROC_SET and PMAPPROC_UNSET from any host. Normally
.Nm
accepts these requests only from the loopback interface for security reasons.
This change is necessary for programs that were compiled with earlier
versions of the rpc library and do not make those requests using the
loopback interface.
.It Fl l
Turns on libwrap connection logging.
.It Fl s
causes
.Nm
to change to the user daemon as soon as possible.
This causes
.Nm
to use non-privileged ports for outgoing connections, preventing non-privileged
clients from using
.Nm
to connect to services from a privileged port.
.El
.Sh SEE ALSO
.Xr inetd.conf 5 ,
.Xr rpcinfo 8 ,
.Xr inetd 8 ,
.Xr syslog 3 ,
.Xr hosts_access 5 ,
.Xr hosts_options 5
.Sh BUGS
If
.Nm
crashes, all servers must be restarted.
.Sh HISTORY
The
.Nm
command appeared in
.Bx 4.3 .
The security features documented herein derive from work by Wietse Venema
at Eindhoven University of Technology, The Netherlands, and first appeared
in
.Nx 1.4 .