This is the last call for comments for the review of debconf templates for portmap. The reviewed templates will be sent on Friday, September 14, 2007 to the package maintainer as a bug report and a mail will be sent to this list with "[BTS]" as a subject tag. --
Template: portmap/loopback Type: boolean Default: false _Description: Should portmap be bound to the loopback address? By default, portmap listens to all IP addresses. However, if this machine does not provide network RPC services (such as NIS or NFS) to remote clients, you can safely bind it to the loopback IP address (127.0.0.1). . This will allow RPC local services (like FAM) to work properly, while preventing remote systems from accessing the RPC services. . This configuration can be changed by editing the OPTIONS line in the /etc/default/portmap file and adapting the use of the -i option to your needs.
Source: portmap
Section: net
Priority: standard
Maintainer: Anibal Monsalve Salazar <anibal@debian.org>
Uploaders: Javier Fernandez-Sanguino Pen~a <jfs@computer.org>
Standards-Version: 3.7.2
Build-Depends: libwrap-dev, debhelper (>= 5)
Package: portmap
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, lsb-base (>= 1.3-9)
Replaces: netbase (<< 4.00)
Description: RPC port mapper
Portmap is a server that converts RPC (Remote Procedure Call) program
numbers into DARPA protocol port numbers. It must be running in order
to make RPC calls.
.
Services that use RPC include NFS and NIS.
.
Homepage: http://neil.brown.name/portmap/
Attachment:
signature.asc
Description: Digital signature