Bug 26493 - portsentry wrongly reports portmap connections
Summary: portsentry wrongly reports portmap connections
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Powertools
Classification: Retired
Component: portsentry
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Powers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-02-07 17:12 UTC by adam.huffman
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2001-02-07 17:13:03 UTC


Attachments (Terms of Use)

Description adam.huffman 2001-02-07 17:12:48 UTC
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 22:51:36 UTC
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.

Tim


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