Bug 26493 - portsentry wrongly reports portmap connections
portsentry wrongly reports portmap connections
Product: Red Hat Powertools
Classification: Retired
Component: portsentry (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Powers
Depends On:
  Show dependency treegraph
Reported: 2001-02-07 12:12 EST by adam.huffman
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-02-07 12:13:03 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 adam.huffman 2001-02-07 12:12:48 EST
On startup portsentry immediately claims there are external portmap
connections, even when I am not dialled up.  It takes up all the CPU time
(along with syslogd, which is logging all the false attack alerts)

This is with no changes to the portsentry config files, and the
security/firewall settings set at installation to "medium".
Comment 1 Tim Powers 2001-02-07 17:51:36 EST
OK. The problem is that it's trying to listen on ports that are already in use.
In this case portmap on 111 is making portsentry freak. I have updated the
config file for this so that logfiles don't get filled with this anymore.


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