Bug 26493

Summary:	portsentry wrongly reports portmap connections
Product:	[Retired] Red Hat Powertools	Reporter:	adam.huffman
Component:	portsentry	Assignee:	Tim Powers <timp>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1	CC:	henris
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-02-07 17:13:03 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 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