Bug 161295 - portmapper prevents unprivileged port access for rstatd
portmapper prevents unprivileged port access for rstatd
Product: Fedora
Classification: Fedora
Component: portmap (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Steve Dickson
Depends On:
  Show dependency treegraph
Reported: 2005-06-21 23:32 EDT by Anthony Thyssen
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-12-06 20:54:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Anthony Thyssen 2005-06-21 23:32:24 EDT
+++ 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 to unset(rstatd): request from
unprivileged port

Version-Release number of selected component (if applicable):

How reproducible:
   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

Note You need to log in before you can comment on or make changes to this bug.