Bug 161295

Summary:	portmapper prevents unprivileged port access for rstatd
Product:	[Fedora] Fedora	Reporter:	Anthony Thyssen <anthony>
Component:	portmap	Assignee:	Steve Dickson <steved>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-12-07 01:54:01 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Anthony Thyssen 2005-06-22 03:32:24 UTC

+++ This bug was initially created as a clone of Bug #155940 +++

Description of problem:

This is the same problem as Bug #155940, but from a different client.

portmap was compiled with -DCHECK_PORT, which prevents it accepting any request
for an RPC service from a non-priviliaged port.

However rstatd clients, such as rup, and xmeter to name common ones are user
informational programs which do not need or want root access to create a
privaliged port.  As such portmap denies ALL requests for rstatd load and uptime
information from these and other load/uptime monitoring clients!

In other words because of this compile time option, rstatd is USELESS!!!
Any attemt to access rstatd is logged with...
     portmap[4431]: connect from 127.0.0.1 to unset(rstatd): request from
unprivileged port

Version-Release number of selected component (if applicable):
portmap-4.0-65
rusers-server-0.17-43
rusers-0.17-43

How reproducible:
Everytime.
   portmap runs by default
   start the rstatd, make sure  rpc.statd is running
   add portmap access to hosts.allow
   try      rup localhost
      rup: localhost: RPC: Unable to receive; errno = Connection refused
   /var/log/messages shows rejection of connection by portmap